241–250 of 385 posts
This is like It Gets Better, but for fragile software engineers who obviously are talented enough to make 6 figures some place else. I understand rejection can feel personal, especially when so much of your life and identity comes from the work you've put into mastering some field, but this doesn't seem like the healthiest mindset. I'm just leaving college now and don't have much of a perspective yet, but the applica…
This is like It Gets Better, but for fragile software engineers who obviously are talented enough to make 6 figures some place else. I understand rejection can feel personal, especially when so much of your life and identity comes from the work you've put into mastering some field, but this doesn't seem like the healthiest mindset. I'm just leaving college now and don't have much of a perspective yet, but the applica…
Earlier quoted context omitted.
ES6 supports classes, so it would be the same thing. > The other thing I find odd is why employers care that someone has deep and existential knowledge of JS? They are probably just bad interviewers, or the company really doesn't know what it wants. Esoteric knowledge questions are a warning signal that you probably don't want to work there.
Most companies, even the best do this. As for TS I'm thinking interfaces, generics etc.
The best one I've come across yet is Brian Acton being rejected by Facebook [0] ends up creating Whatsapp and in turn selling it to Facebook for $19B. Talk about comebacks. [0] https://twitter.com/brianacton/status/3109544383?lang=en
On the other hand, if Facebook had hired him, it's unlikely he would have had enough freedom to create Whatsapp or anything like it. Even if Facebook knew what was going to happen, Facebook still made the right choice when they rejected him and later bought his company. Rejection can be a good thing for everyone.
Seems like a lot of people went on to be hired by twitter after not satisfying some other hiring processes. What if this just means that twitter hires second rate people? Also, I wouldn’t have hired the guy who doesn’t use semicolons in his JavaScript, either.
I used to hate when I saw JS with semicolons too. "Get off my lawn" with that naked code! Not sure when or how it changed, but I'm on the other side of the fence now. Without semicolons (unless multi-statements on a single line), JS is so much cleaner. A line break is perfectly sufficient to signal the end of a statement.
This really highlights how hard it is to hire, at least in Tech. We come up with processes and fantastic lists of questions that verify how well a candidate knows minutia, and use that as proxy for how well he/she will do in a position where the primary required skill is speed of learning and growth. I'll hire someone who knows how to find out what they are missing over someone who knows a lot of details but can't gr…
If there are two good candidates and I pick one of them, it doesn't necessarily mean you were 'rejected', you just weren't selected. I've been 'rejected' by plenty of companies but I try not to take it too personally.
Passive voice. This is the type of weasel language that people try to use to make themselves feel better about what they did. Unless you cleverly redefine rejected to have some additional baggage, the phrase 'not selected' and 'rejected' are semantically equivalent. At least do the people you don't pick the courtesy of owning up to your decision.
Earlier quoted context omitted.
When I was a senior at university, my friends and I all had a wall at our apartments covered with our rejection letters. Back then (if they gave you the courtesy of a reply) they were sent on paper in the mail. So yes, it's always been that way. I myself have been on interview committees and voted to reject candidates who got hired, and turned out to be good. Why did I want to reject them? Don't really know, just got…
I did this when I was a math undergrad applying for grad school. I applied to 15 graduate programs and got into 10, and rejected by 5. The surprising pattern was that I got into a graduate program if and only if it wasn't in the Northeast; selectivity of the program didn't seem too relevant. After graduate school, for my first job I ended up being on the graduate admissions committee at the Harvard Mathematics depart…
Admit the "no brainers" in the upper right. Reject the "no ways" in the lower left. Then take a harder look at those in the middle. But the reality is that you could probably take an arbitrary subset of the middle group and they'd probably do nearly as well/contribute as much/etc. as the final selection you sweated over.
I've also been on the selection committee for various conferences over the years and that also often ends up working the same way to a significant degree.
This is like It Gets Better, but for fragile software engineers who obviously are talented enough to make 6 figures some place else. I understand rejection can feel personal, especially when so much of your life and identity comes from the work you've put into mastering some field, but this doesn't seem like the healthiest mindset. I'm just leaving college now and don't have much of a perspective yet, but the applica…
So let's take it as an assumption that the people that this is for are "fragile software engineers." How would you address that fragility? Certainly, having monetary success does not necessarily address feelings of inadequacy. It's also very difficult to bootstrap oneself out of such feelings. One way to address it is to share and know that you're not alone. That's exactly what this attempts to do. Simply dismissing…