Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "first rejection"
-
current stage of development at work
anger and rejection at first but now ends up at acceptance and sarcasm4 -
Well I ended my interviews-adventure finally.
Applied for three companies:
- KindOfBigCompany
- BiggestCompany
- BiggestCompany2
I failed in the last two. But got the job in the first one.
The bittersweet sensation is that I got the job in the first one first and then got rejected by the other two so my last feeling is the rejection one. And I really liked BiggestCompany2.
BUT KindOfBigCompany is actually really cool and has a lot of benefits and also I'll earn much more than I currently am so I guess Happy Ending after all :D5 -
I was laid off right before Christmas because my manager would not give me any work (bully.. possibly discrimination). I asked for work to do for 2 weeks, even coming up with things to contribute on my own. My contributions were rejected and the lead developer agreed with me that it was fucked up but did nothing. The little work that I was given was always completed above standard and the lead dev had made comments praising my self tasked contributions but each rejection I was told it would be shelved for version 1.2.
Finally fed up, feeling as though I was being completely ignored, I told the lead dev I was going home half day early if there was nothing for me to do. The next day the CTO fired me and even lied to my recruiter telling him that I had not shown up for work for 3 days (easily disproven).
It's now the first of the year, probably not the best time to be looking for a new job, and my current outlook is that I am not going to be able to pay my rent at the end of the month.
My motivation has diminished, my confidence is gone. Job prospects are few. I don't know how to proceed.9 -
So for everyone looking for a job, that keeps getting rejection or crickets I'll give you the following tip.
Most of the first level screen of resumes are done by automated machines that are basically just doing keyword matching. So if you want your resume to get through more of these automated scanners, what you do is create a second page on your resume and cram it with every keyword, and buzzword you can thinking of, like "10 years react experience." "20 years java architect", "AR/VR 5 years", "15 years mobile", etc ,etc.
Then select the text and change it to white. No human being will see it, but the automated scanners will and rocket you to the top of the list.
Your welcome. Now help me get my penguin!6 -
Okay, story time.
Back during 2016, I decided to do a little experiment to test the viability of multithreading in a JavaScript server stack, and I'm not talking about the Node.js way of queuing I/O on background threads, or about WebWorkers that box and convert your arguments to JSON and back during a simple call across two JS contexts.
I'm talking about JavaScript code running concurrently on all cores. I'm talking about replacing the god-awful single-threaded event loop of ECMAScript – the biggest bottleneck in software history – with an honest-to-god, lock-free thread-pool scheduler that executes JS code in parallel, on all cores.
I'm talking about concurrent access to shared mutable state – a big, rightfully-hated mess when done badly – in JavaScript.
This rant is about the many mistakes I made at the time, specifically the biggest – but not the first – of which: publishing some preliminary results very early on.
Every time I showed my work to a JavaScript developer, I'd get negative feedback. Like, unjustified hatred and immediate denial, or outright rejection of the entire concept. Some were even adamantly trying to discourage me from this project.
So I posted a sarcastic question to the Software Engineering Stack Exchange, which was originally worded differently to reflect my frustration, but was later edited by mods to be more serious.
You can see the responses for yourself here: https://goo.gl/poHKpK
Most of the serious answers were along the lines of "multithreading is hard". The top voted response started with this statement: "1) Multithreading is extremely hard, and unfortunately the way you've presented this idea so far implies you're severely underestimating how hard it is."
While I'll admit that my presentation was initially lacking, I later made an entire page to explain the synchronisation mechanism in place, and you can read more about it here, if you're interested:
http://nexusjs.com/architecture/
But what really shocked me was that I had never understood the mindset that all the naysayers adopted until I read that response.
Because the bottom-line of that entire response is an argument: an argument against change.
The average JavaScript developer doesn't want a multithreaded server platform for JavaScript because it means a change of the status quo.
And this is exactly why I started this project. I wanted a highly performant JavaScript platform for servers that's more suitable for real-time applications like transcoding, video streaming, and machine learning.
Nexus does not and will not hold your hand. It will not repeat Node's mistakes and give you nice ways to shoot yourself in the foot later, like `process.on('uncaughtException', ...)` for a catch-all global error handling solution.
No, an uncaught exception will be dealt with like any other self-respecting language: by not ignoring the problem and pretending it doesn't exist. If you write bad code, your program will crash, and you can't rectify a bug in your code by ignoring its presence entirely and using duct tape to scrape something together.
Back on the topic of multithreading, though. Multithreading is known to be hard, that's true. But how do you deal with a difficult solution? You simplify it and break it down, not just disregard it completely; because multithreading has its great advantages, too.
Like, how about we talk performance?
How about distributed algorithms that don't waste 40% of their computing power on agent communication and pointless overhead (like the serialisation/deserialisation of messages across the execution boundary for every single call)?
How about vertical scaling without forking the entire address space (and thus multiplying your application's memory consumption by the number of cores you wish to use)?
How about utilising logical CPUs to the fullest extent, and allowing them to execute JavaScript? Something that isn't even possible with the current model implemented by Node?
Some will say that the performance gains aren't worth the risk. That the possibility of race conditions and deadlocks aren't worth it.
That's the point of cooperative multithreading. It is a way to smartly work around these issues.
If you use promises, they will execute in parallel, to the best of the scheduler's abilities, and if you chain them then they will run consecutively as planned according to their dependency graph.
If your code doesn't access global variables or shared closure variables, or your promises only deal with their provided inputs without side-effects, then no contention will *ever* occur.
If you only read and never modify globals, no contention will ever occur.
Are you seeing the same trend I'm seeing?
Good JavaScript programming practices miraculously coincide with the best practices of thread-safety.
When someone says we shouldn't use multithreading because it's hard, do you know what I like to say to that?
"To multithread, you need a pair."18 -
College can be one of the worst investments for an IT career ever.
I've been in university for the past 3 years and my views on higher education have radically changed from positive to mostly cynical.
This is an extremely polarizing topic, some say "your college is shite", "#notall", "you complain too much", and to all of you I am glad you are happy with your expensive toilet paper and feel like your dick just grew an inch longer, what I'll be talking about is my personal experience and you may make of it what you wish. I'm not addressing the best ivy-league Unis those are a whole other topic, I'll talk about average Unis for average Joes like me.
Higher education has been the golden ticket for countless generations, you know it, your parents believe in it and your grandparents lived it. But things are not like they used to be, higher education is a failing business model that will soon burst, it used to be simple, good grades + good college + nice title = happy life.
Sounds good? Well fuck you because the career paths that still work like that are limited, like less than 4.
The above is specially true in IT where shit moves so fast and furious if you get distracted for just a second you get Paul Walkered out of the Valley; companies don't want you to serve your best anymore, they want grunt work for the most part and grunts with inferiority complex to manage those grunts and ship the rest to India (or Mexico) at best startups hire the best problem solvers they can get because they need quality rather than quantity.
Does Uni prepare you for that? Well...no, the industry changes so much they can't even follow up on what it requires and ends up creating lousy study programs then tells you to invest $200k+ in "your future" for you to sweat your ass off on unproductive tasks to then get out and be struck by jobs that ask for knowledge you hadn't even heard off.
Remember those nights you wasted drawing ER diagrams while that other shmuck followed tutorials on react? Well he's your boss now, but don't worry you will wear your tired eyes, caffeine saturated breath and overweight with pride while holding your empty title, don't get me wrong I've indulged in some rough play too but I have noticed that 3 months giving a project my heart and soul teaches me more than 6 months of painstakingly pleasing professors with big egos.
And the soon to be graduates, my God...you have the ones that are there for the lulz, the nerds that beat their ass off to sustain a scholarship they'll have to pay back with interests and the ones that just hope for the best. The last two of the list are the ones I really feel bad for, the nerds will beat themselves over and over to comply with teacher demands not noticing they are about to graduate still versioning on .zip and drive, the latter feel something's wrong but they have no chances if there isn't a teacher to mentor them.
And what pisses me off even more is the typical answers to these issues "you NEED the title" and "you need to be self taught". First of all bitch how many times have we heard, seen and experienced the rejection for being overqualified? The market is saturated with titles, so much so they have become meaningless, IT companies now hire on an experience, economical and likeability basis. Worse, you tell me I need to be self taught, fucker I've been self taught for years why would I travel 10km a day for you to give me 0 new insights, slacking in my face or do what my dog does when I program (stare at me) and that's just on the days you decide to attend!
But not everything is bad, college does give you three things: networking, some good teachers and expensive dead tree remnants, is it worth the price tag, not really, not if you don't need it.
My broken family is not one of resources and even tho I had an 80% scholarship at the second best uni of my country I decided I didn't need the 10+ year debt for not sleeping 4 years, I decided to go to the 3rd in the list which is state funded; as for that decision it worked out as I'm paying most of everything now and through my BS I've noticed all of the above, I've visited 4 universities in my country and 4 abroad and even tho they have better everything abroad it still doesn't justify some of the prices.
If you don't feel like I do and you are happy, I'm happy for you. My rant is about my personal experience which is kind of in the context of IT higher education in the last ~8 years.
Just letting some steam off and not regretting most of my decisions.15 -
It was my first time in Berlin. I came as a tourist but started looking for a workplace, with hopes of getting a blue card and continuing work.
I searched online, going through some hiring platforms, and sent out a few messages around. I felt a special connection (I thought I was exactly who they needed), and wrote them a carefully crafted letter of intention alongside my lavish CV.
They got back to me, and I was given this task, to do while at home. I completed it, had a phone interview, and was invited on-site for a face to face interview. Everybody felt warm, I felt a connection. We already talked salary expectations, and all was going great.
They told me they'd get back to me for the next stage. ...
and they actually DID. Yes, they did!
They invited me for a second interview, but this time to prepare a technical topic to present. So I did. I picked one of the 3 topics they offered, which was about performance optimization. I had recently read materials about that, so I felt really empowered.
So far nobody told me what I was supposed to be doing at the new job, I only knew the technologies required, and what the company did for money.
I prepared a thorough presentation, with practical demos of why some things are bad for performance. While I was showing it, many people in the room were learning about this for the first time, which means I did good. The team lead had some extra questions that I wasn't able to answer in full (needed some research), but otherwise it was great.
The CTO then asked me out to lunch, to talk over some more stuff, and we had a general discussion about what drives us, our life story, etc. He said that he'd really like me to be part of the team, and that he's looking forward to working with me.
So I've been at it for almost a month. I've met everyone, got acquainted with the team, knew the biography of some of them, proven my worth, etc. I was ensured with body language, and verbal language that everything was going great. As careful as I was with this kind of stuff, I was positive that I'd get the job. I even started planning my trips, to get the documents ready.
And then I got a message stating the usual stuff "Thank you bla bla bla we don't think we'll need your services". I was shocked, but in good faith I wanted to reply something along the lines "I'm sorry it didn't work out, all the best in finding what you're looking for", but I found out that I was blocked from contacting them.
That's right. Rejected + blocked. After a month of fucking foreplay. I get rejection, even though it hurts. But being blocked?! That's just insane!8 -
The worst boss and human being so far, still wondering how he keeps the company afloat. This was my first longterm developer job almost a decade ago and I was a student at that time. The application was an outlook plug in for a document management system.
Scene 1:
Boss: The processing is too slow. Make it faster.
Me: After analysis and profiling I can prove that the core (developed in VB6 by a physicist and autoconverted to VB.NET) is the bottleneck.
Boss: I don't care. Make it faster and don't touch the core.
Scene 2:
Boss: I want the app to behave in that way.
Me: This is not what we specified previously. Look here. Nonetheless, I would have to rewrite half of the plugin. Mind that it is an outlook plug in and we are restricted by outlook. If you want that, it would take XX days and we do not have enough time until release.
Boss: I don't care. Do it. And the deadline stays as it is.
Boss 2 weeks later: I don't like it.
Scene 3:
Me: To release in time I need more resources. I need at least one tester and another developer would be a huge plus. Also, I need a second PC for testing.
Boss: No.
2 weeks later:
Boss: why does it not work properly in outlook 2010? Didn't you test it?
Me: I could not. I have only outlook 2007. I asked for more resources and did not get them.
Boss: it's your fault. Bad work.
Scene 4:
*Me having failed multiple exams, stress at work, started to drink*
Boss: Don't you like working here?
Me: ...
Finale:
*Me getting written sick with severe depression*
Boss: fires me.
Me: Loses flat. Quits uni. Unemployed for 6 Months, one rejection after another (boss was phoned, that's sure). Moving back to parents. Sues boss. Gets money.
I still hate him and wish him the most painful experiences in life. Such people belong behind bars. But the justice isn't always served. One has to move forward and improve himself.3 -
Most embarrassing interview rejection was not even in person, it was over the phone.
The company that I was going to work for (quite a big one mind you), scheduled to phone me at 2PM, I was preparing mentally for 2PM, so I took my girlfriend to lunch at 1. Just to relax and calm myself before the phoned me.
It was 34 degrees (celcius - I think that's about 93 farenheit? somewhere close) outside and I was waiting for her to finish her smoke (she was in the smoking area).
They phoned me, and it caught me completely off-guard. My years of knowledge just seemed to flush down the toilet at that moment, and I utterly felt stupid talking to the guy over the phone. It was a first for me, and I hope that it never happens again - he basically stopped me, told me that I had better not apply before I know what I am talking about (as I was wasting his time), and then put down the phone on me..
Worst part was that my girlfriend came back right then and asked me if I am ready for the interview. I hung my head in shame because I was ashamed to tell her that I fucked it up, because you know, I kind of needed the job (the one I had at the stage was shitty).1 -
I wouldn't say it's upsetting but confusing.
I had an interview at a household name where I asked for feedback. They only told me I did well in the technical and every other area, and that I was the first person they interviewed in the last 2 months to make it passed the technical part.
Less than half a day later I got a rejection email.3 -
Got my first rejection after my first job interview via e-Mail today. It was about a local webhosting company.
I feel a little bit sad about it, but I am glad that I have made this experience with them and hope that I can use this experience to better myself in future job interviews.
What bothers me the most is that they told me in the mail that they are sad to send that rejection mail to a friendly and warm person like me, but they do not give a clean explanation why they had to reject me.
Was it because of someone better than me? Am I not qualified enough? What is the reason ffs?
I have send them a mail back mentioning that I am thankful for the conversation we have had, but also asking for the reason of the rejection.
I do not think that they will reply me back, but I hope they will.5 -
Just got a rejection email from the only interview I’ve gotten.... I know it’s normal but I feel so dejected and imposter-syndromey. When I get rejected from a non dev job it doesn’t make me question my ability, but because this is the first time sending out dev resumes it’s so daunting and I feel useless😞5
-
First time dealing with the rejection process from Apple, and it couldn't be more frustrating. I asked for clarification 3 times and got the same exact response all 3 times... LET ME TALK TO A FUCKING HUMAN!
-
Headhunter called about a rejection for an assignment I did:
Assignment had malformed data examples
Assignment had unrealistic timespan for completion
Assignment used item stocks for a shop setup
Assignment didn't use any prices just item stocks
Who builds a webshop without prices in the first place?
So done with this job hunting assessment bullshit.3 -
!dev
I went on a date over two weeks ago. It seemed to go well, but the next week she called me and said she wasn't interested, giving reasons why.
I was disappointed but responded as friendly and responsibly as possible. It was the first time a girl had said no to me, so it hurt.
While it hurt to be rejected, I also felt relief because her reasons prevented us from continuing down a path of mismatched expectations.
The next day, I told a close friend about the outcome of the date because he knew of my interest in the girl. We talked and laughed about it like a missed train on a rainy day.
Just last night, my friend told me he met with the girl, and I was shocked. He said he didn't know why she had said no and wanted to talk to her to try to change her mind.
I was angry because I felt this was a dumb move. He said he was only trying to help because he thought she was a good match for me.
I had already closed that chapter and moved on, so I told my friend I didn't care what they discussed and that I had seen her missed call on my phone. If she calls me again, I won't pretend everything is okay and will let her know that I never sent my friend to convince her further.
He told me to pick up her call and hear her out, but I personally find it disturbing if someone needs to be convinced by a friend to get a positive response.
Yes. I was disappointed by the rejection, but I respected her decision. I was frustrated by my friend's actions, but I will stick to my decision and not pretend everything is okay if she contacts me again.
She just sent a text now! oh my f*cking friend…7 -
Still looking for my first full-time dev role. After being endlessly rejected from every dev job I've applied for, it starts to eat away at your confidence. Makes me wonder if I'm not as competent as I believe I am. :/
Fortunately, I landed a coding interview with Google! It is my dream job to work at Google, so the fact that they even acknowledged me & my skillset makes me so happy and reaffirms my belief in my capabilities. :D
It's pretty odd, that after applying to 20+ open Google positions relevant to my skill level & location and often with references included, then having been rejected from all of them, that I finally got a chance with them when one of their recruiters found me on LinkedIn and liked what she saw. I cleared the screening call, and made it to the first coding interview.
Of course, even with all the interview prep I've done, it was all practically for naught since they caught me off guard with a crazy conceptual problem anyway. (Well, actually, was I 'caught off guard' if I was already expecting to be caught off guard? o.0) I struggled heavily in the first half of the interview, but found my footing towards the end. So I knew I screwed up and that it was highly unlikely for me to get the job.
Nonetheless, Google had the decency to reject me not via an automated email, but through an actual direct phone call with my recruiter. (The cruelty of the automated application rejection system in our society is a whole rant of its own, for another time.) My recruiter told me that they felt I wasn't ready but they liked what they saw, so they will be revisiting me in exactly a year to reconsider me.
To know that I wasn't fully rejected, and that my dream company Google sees real potential in me, is highly reassuring. It means I'm not a lost cause; I simply need to keep looking. Google will want me more strongly once I have the experience that comes from a fresh grad's first full-time job.7 -
The worst rejection was one after a first interview and a subsequent 3 hour code challenge. I was super nervous as it was my first code challenge in an interview that was one of my first. I wasn't confident when I submitted my work, but the time was up and so there wasn't much to be done.
The rejection was simple. Pure silence. No arguments, or feedback. Just didn't hear nothing back and that didn't help my fresh out of university self-confidence.1 -
I got a new job recently(that's an older rant's story) and I find amusing that I'm still getting reject notices from job offers which I applied to... 2 months ago 😂
That one from 2 months ago is quite funny cuz I didn't have any other interview with the company, just like the first interview with a HR lady, so after one week I gave up with that company and moved on. So I received the rejection notice today and my first thought was "how considerate!"5 -
In the last module of my bootcamp(make all the jokes you want about bootcamp I have thick skin and a degree 😬) and just started applying for jobs. First job I applied for was a big company asking for 5+ years experience.
Might as well get used to rejection early 😂3 -
End of my rant about 35 day recruitment process for anyone interested to hear the ending.
Just got rejected by a company (name Swenson He) for a remote Android Engineer SWE role after wasting 35 days for the recruitment process.
First intro interview went good, then I did an assignment that had 72 hours deadline (asked for couple days longer to do this task, did it in around 40 hours, it was purely an assignment not free work, I could have done it in a day but I choose to overeenginer it so I could use the project as a portfolio piece, no regrets there and I learned some new things). After that It took them 2 weeks just to organize the technical interview.
2 days after the technical interview I received an offer from a second company with 1 week to decide. I immediately informed the Swenson He about it and politely asked whether they could speed up their decision process.
Now I know that I could just sign with the second company and if the big Swenson He would decide to bless me with and offer I could jump ship. But out of principle I never did that for 7 years of my career. If Im in a situation with multiple offers I always inform all parties (it's kinda a test for them so I could see which one is more serious and wants me to work for them more). Swenson He didnt pass the test.
6 days of silence. I pinged the techlead I interviewed with on LinkedIn about my situation, he assured me that he'l ask his hiring team to get back to me with feedback that day.
2 days of silence. I had to decide to sign or not to sign with a second company. I pinged the techlead again regarding their decision and 10min after received a rejection letter. There was no feedback.
I guess they got pissed off or something. Idk what were they thinking, maybe something along the lines of "Candidate trying to force our 35day recruitment process to go faster? Pinging us so much? Has another offer? What an asshole! ".
Didnt even receive any feedback in the end. Pinged their techlead regarding that but no response. Anyways fuck them. I felt during entire process that they are disrespecting me, I just wanted do see how it ends. Techlead was cool and knowledgeable but recruitment team was incompetent and couldn't even stay in touch properly during entire process. Had I didn't force their hand I bet they would have just ghosted me like they did with others according to their Glassdoor reviews.
Glad I continued to interview for other places, tomorrow Im signing an offer. Fuck Swenson He.
P.S. From my experience as a remote B2B contractor if a company is serious the entire process shouldn't take longer than max 2 weeks. Anything outside of that is pure incompetence. Even more serious companies can organize the required 2-3 meetings in a week if they have to and if they are interested. Hiring process shouldnt take longer than MAX 3 weeks unless you are applying for some fancy slow picky corporate company or a FAANG, which is out of topic for this post. -
I wouldn't call any rejection worst.
I learnt new things everytime I had interview actually they came to me like steps of learning and when I get to know enough I got my first job :) -
Have had multiple interview rejections already at 20. Strongly feel I am bad at it.
Maybe it's because these are my first few interviews and/or that I'm still in college and don't realise how interviews work.
Really hard not to grudge the interviewer after a rejection. Cunts all of them.
Share your story/opinion if you feel like.2 -
"Reviewer 2 is always a bitch"
Aaaaaaaand I'm looking at gloomy reviews which means my paper is gonna get rejected soon. Why oh god why!
(Actually, I know why, and maybe this is for the best, since I pulled the method out of my arse because I found out environments were unstable and had to nag about it to not fully lose a year's worth of investigative work. But also, this is my first conference rejection. Literally. 😐)
... There's a slight chance one of the reviews might save me tho, so keep your fingers and toes crossed for me, pleaeaeaeaeaeaeaaeaease! 🙏🏻8 -
When i hire devs at my company i will treat them exactly the same way i was treated.
At first I'll hire by normal procedures top level engineers so my company can live. And then I'll continue hiring even after all positions are closed. I'll fuck with all the engineers and anyone who wants to work for me by exactly the same way i was getting fucked with by 20+ companies -- I'll drag them around with 3+ interviews over the course of 4+ weeks and even if they fulfill all the requirements and knowledge and skills i require, I'll STILL reject them and degrade their self esteem. Fuck you. I'll fuck you up and degrade you and make you feel worthless -- exactly the same as i was treated.
I'll give them a vague rejection letter, that doesn't explain why they got rejected. Or just make up some bullshit reason for rejection that isn't even true. I'll also wait 2+ weeks additionally until i respond with rejection letter, just to fuck with people even more -- exactly the same way as i was treated.
If they put they have 7+ years of experience, I'll reject them because of not having 8+ years of experience -- exactly the same way as i was treated.
If they answer all technical questions correctly, I'll reject them and tell them I chose another candidate because they fit better -- exactly the same way as i was treated.
If they pass through 4 interviews after 1 month of interviews, I'll give them a positive feedback. And then ghost them with no response -- exactly the same way as i was treated.
On technical interviews I'll ask them some ridiculous questions no one knows and are not related to their job position, and then reject them for not knowing those answers -- exactly the same way as i was treated.
On HR interviews I'll milk the information from them of projects and clients they worked with, and then contact those clients to steal them from him so i can earn money and reject him instead with a vague reason -- exactly the same way as i was treated.
I'll give the developer a whole ass project to develop over the course of 10+ days, and then reject them for a vague reason, and use their source code to sell to my client while developer worked for 0$/hour and i got paid thousands -- exactly the same way as i was treated.
I now LIVE to build a company not because i want to earn money, not because i want to have a company, not because i like engineering (although all of those are true and i want to achieve), but now a NEW top priority goal and REASON i want to have a company -- is so i can be able to abuse innocent people mentally and psychologically. Degrade people. DESTROY their self esteem. I LIVE FOR THIS NOW. I AM FUCKING TIRED OF GETTING TREATED LIKE THIS UNDESERVINGLY AND NOT HAVING THE OPTION TO FIGHT BACK. I WILL NOW FIGHT BACK BY DOING THE SAME THING TO OTHER PEOPLE WHO ARE STRUGGLING AND DESPERATELY LOOKING FOR A JOB. I WANT TO CAUSE HARM AND VIOLENCE PSYCHOLOGICALLY.
EXACTLY. THE SAME. WAY. AS. I. WAS. TREATED.25 -
I'm just fed up with the industry. There are so much stupidity and so much arrogance.
My professional experience comes mainly from the frontend and I feel like it's not as bad on the backend but I'm still convinced it's not really different:
I'm now about to start my 3rd job. It's always the same. The frontend codebase is complete shit. It's not because some juniors messed up not at all. It's always some highly paid self-proclaimed full-stack developer that didn't really care somehow hacked together most of the codebase.
That person got a rediculous salary considering the actual skill and effort that went into the code, at some point things became difficult, issues started to occur and that person left. If I search for that person I find next to the worst code via gitlens on Linkedin it's somebody that has changed companies at least two times after leaving and works now for a lot of money as tech-lead at some company.
There's never any tests. At the same time the company takes pride in having decent test coverage on the backend. In the end this only results in pushing a lot of business logic to the frontend because it would just take way to long to implement it on the backend.
Most of the time I'm getting told on my first day that the code quality is really high or some bullshit.
It's always a redux app written by people, that just connect everything to the store and never tried to reflect about their use of redux.
Usually it's people, that never even considered or tried not using redux, even if it's just to learn and experiment.
At the same time you could have the most awesome projects on github but people look at your CV, sum up the years and if you invested a lot of time, worked way harder to be better than other developers with the same amount of experience, it's totally irrelevant.
At the same time all companies are just the worst crybabies about not being able to find enough developers.
HR and recruiters are generally happy to invite somebody for an interview, even if that person does not have any code available to the public, as long as that person somehow was in some way employed in the industry for a couple of years. At the same time they wouldn't even notice if you're core contributor for some major open-source product if you do not have the necessary number of years in the industry.
I'm just fed up.
By the way, I got my first real job about two years ago. Now I'm about to start my third position because my last job died because of the corona crisis. I didn't complain for some time because I didn't want to look like I'm just complaining about my own situation. With every new job I made more money, now I'm starting for the first time at a position that is labeled "lead" in the contract.
So I did okay. But I know that lots of talented people that worked hard gave up at some point and even those that made it had to deal with way too much rejection.
At the same time there are so many "senior" people in the industry, that don't care, don't even try to get better, that get a lot of money for nothing.
It's ridiculously hard to get a food in the door if you don't have any experience.
But that's not because juniors are actually useless. It's because the code written by many seniors is so low quality, that you need multiple years of experience just to deal with all the traps.
Furthermore those seniors are so busy trying to put out the fires they are responsible for to actually put time into mentoring juniors.
It's just so fucked up.3 -
Just closed my first job contract today... Haven't signed yet, but feels good! Haven't had to face rejection :) (yet)7
-
Aaaaand another rejection. Without a reason. And only after i asked about the status. I guess if i didnt ask, i wasnt told in the first place. Bastards. Meanwhile i’m kinda broke now. There goes my savings!4
-
How many times have u told a company that you will not be moving forward with the interview process bc you accepted an offer... only to have them send you a rejection letter 45 mins later??? 😂😂😂 Happened to me yesterday.
Told 3 companies that.
I didn't really expect them to respond, just wanted to let them know.
First company: No response.
Second company: Wished me well and thanked me for the update.
Third company: Sent me a rejection letter.
I'm like, "You guys just couldn't resist, huh?" 😂5 -
They offered a coding test alongside a resume. So I took it and did extremely well. Showcased my talents wonderfully. They ask for an interview (video call). We do the first half of the interview with an HR rep, goes great, a little over schedule. So we go into the second half with a little over twenty minutes left, and the hiring engineer wants me to write some code. He explains my task and sends me to a site where I can write and execute the code and he can watch. I had never written code with an audience before, and between that and my now 20 minute timer, I was a tangled up ball of nerves. Needless to say, I blew it, writing nothing of worth. He ends the call and I open my IDE. Working solution in 7 minutes. I got a rejection email two days later. Worst part? The company employed the author of one of my favorite "learn to code books". Would have been amazing to work with him. Really demotivating to say the least.2
-
I had my first trivia yesterday. I made so many dumb mistakes simply because I was nervous due to it being a test.
After it was over I implemented the solution that I fucked up in one of the puzzles.
Good start, I guess. I at least got 50% right, but I expect a rejection due to forgetting random facts, plus the failure to answer the embarrassingly easy puzzle that just required a stack and a reverse loop.
I need to desensitize myself.1 -
Top 5 Reasons for Not Discussing Weird Topics in Your Graduate Admission Essay
Knowing the top five reasons for not discussing weird topics in your graduate admission essay is very important. There is really no strict requirement about what kind of topic you use, as long as you can discuss it effectively. However, choosing weird topics may not really work for you, especially if it’s a very controversial or sensitive one. The following are the top five reasons why you should avoid discussing weird topics in your essay.
Reason #1: Weird topics are weird.
First off, weird topics are exactly that, weird. The last thing you want to do is weird out your graduate school admission panel, which is almost a sure way of getting yourself that polite rejection letter that every applicant dreads of receiving.
One of the main important points to remember is to think of your audience when writing your graduate admission essay. This audience will be composed of tenured professors, and probably younger teachers closer to your own age. Although it is a good idea not to tailor your essay according to what you think they want to hear, it’s best to stick to a topic that will make the panel want to get to know you more. You can do this by putting yourself in the admission officer’s shoes and trying to feel what your reaction would be with a particular topic you have in mind. Being creative is good, but to any audience, weird is weird, and most audiences will not know how to react to a weird admission essay.
Reason #2: Weird topics may reflect your personality in a bad way.
Weird topics make you look weird, or worse. You may think that a weird topic is the same as a creative topic, something that most experts on admissions officers urge applicants to use. With a weird topic, you can easily make the jump from being creative to just plain strange or worse, someone with an emotional or personality problem. Weird topics, when discussed ineffectively, are bad topics, and can be anything from the death of a pet, recent religious epiphanies, and even parent bashing. These topics are the last topics that can paint you in a good light so avoid these and other similar topics.
Reason #3: Weird topics may not represent the real you.
Weird topics will not paint the real you, unless you are naturally weird. If you really think that being a little bit off will pay off, then by all means do so. But if you want to appear as normal and as emotionally healthy as possible, save the strange stories for Halloween night.
Reason #4: Weird topics may seem too informal.
Weird topics can get too informal. You can be informal but you need to look normal as well in order to avoid appearing irreverent. Some may disagree with this, but often the only way to get on your admission panel’s good side is to tread on the middle ground arefully, and not be too stiff and prudish but not be too loose either.
Reason #5: Weird topics may confuse the readers.
While most schools allow their applicants free reign when it comes to writing an admissions essay, you can do your self a lot of good by treading on the middle ground. Avoid weird or strange topics if you can. A weird topic will put your readers in a place where they may not understand you. And in a process where getting to know you as a person is the main objective, this move will definitely have an effect on whether you get accepted or not. Knowing what to write in a graduate school admission essay is fairly easy, especially if the school provides you with a set of questions, known as prompts as your guide. As long as you already have the other requirements such as the right grade point average, recommendation letters, program of study and the like, you can start working on your essay. But if your still not sure whether it good idea to write essay by yourself. You can find tons of great quality writing services such as https://uk-essays.com/research-pape.... At such a websites you’ll easily find help from from people who already have considerable experience in writing a wide variety of essays. They will gladly help in any issue that makes you difficult.