471–480 of 482 posts
Earlier quoted context omitted.
While I meant globally, and I’m not sure that these stats generalize beyond the US (but they very much might), I’m surprised! I had expected 2/3rd to work at companies under 1000 employees simply because there’s so extremely many of those and many of them need devs. EDIT woa that page says there’s 320k software engineers in the US. That’s one entire percent of the population! That’s a lot, could that really be true?
That’s 0.1%, actually.
Earlier quoted context omitted.
[flagged]
This is not a good strategy. Your job is likely not as secure as you think, particularly once you are legitimately elderly.
All joking aside, it seems to be the one area that only wants the elderly.
Earlier quoted context omitted.
I haven't had a job interview without leetcode bullshit in about 15 years. And years before that. Basically since Joel's posts in the early 2000s. He promoted a reasonable idea-that programmers should know how to program. Then B and C players rushed to make that happen! Similar to how agile became the complete opposite of what it meant originally.
As a counter-point, I've almost never had a job interview depend on leetcode-type problems in my ~20 years.
If you've got networking to let you bypass the BS, that's great. But most interviews (by number) are "cold" interviews that conduct these almost exclusively. Due to lack of trust and extreme fear of failure.
The only offer I've received in years was because, while they did this type of test as well, they didn't take the results too seriously. One out of maybe a hundred attempts that year.
Blog posts like these are a staple on HN and I’m always mildly offended by them. It seems to me that there’s a class of programmer that will take an overpaid job at a terrible BigCo, spend their evenings writing ranty blog posts about how terrible it all is, culminating in the inevitable “I quit” article, only subsequently to accept a job at a different terrible BigCo. At no point does this article, or most articles…
Not a major driver of improvement, that there attitude.
I love how the author is just too busy solving problems brought about by idiots (not him, of course), but never mentions solving problems via: 1. Improving dashboard engagement through awareness. Maybe through something like periodic email blasts that showcase metrics from the dashboards. 2. Mentoring some of the subpar engineers to help them improve so that future issues ebb and overall quality increases. But, no, t…
Blog posts like these are a staple on HN and I’m always mildly offended by them. It seems to me that there’s a class of programmer that will take an overpaid job at a terrible BigCo, spend their evenings writing ranty blog posts about how terrible it all is, culminating in the inevitable “I quit” article, only subsequently to accept a job at a different terrible BigCo. At no point does this article, or most articles…
If we lived in a world where money wasn't so important I would fully agree with you. But it is. I can't earn the same as you all can because I don't live in the US, but if I did I would grind all the leetcode (as insulting as I find them) for one single reason: I don't want to work forever. So I agree with some other comments here. No it's not really a choice. Choosing to earn less and hope for a lottery ticket win l…
Earlier quoted context omitted.
> I don't live in the US, but if I did I would grind all the leetcode (as insulting as I find them) for one single reason: I don't want to work forever. I find it funny that the internet exaggerations have convinced non-US people that: 1. Doing a couple LeetCode problems is the only thing interviewers look for 2. Everyone here automatically gets a high paying FAANG-like job if they can memorize enough LeetCode proble…
I haven't had a job interview without leetcode bullshit in about 15 years. And years before that. Basically since Joel's posts in the early 2000s. He promoted a reasonable idea-that programmers should know how to program. Then B and C players rushed to make that happen! Similar to how agile became the complete opposite of what it meant originally.
The most jarring thing about entering the workforce to me, and it seems to the author as well, is the nigh-pathological lack of pride (or “passion”, which I think is a loathsome term) most people put into their jobs. I don’t accept that all of those people intrinsically are lazy morons - maybe some or even most are, but a lot of people get that attitude metaphorically beaten into them by lazy and disengaged coworkers…
Which companies do things "right"? How do I select for them when interviewing? Also, how do I know that _I'm_ not the one who's wrong?
I'd look for companies led by conscientious founders.
I love the idea of working for a startup, but I want to be paid well and avoid too much risk.
From what I know, those goals aren't really compatible with startups.
Earlier quoted context omitted.
How? Programmers don't have executive powers. You are very often told that this is not your job and you should be doing yours and leave the "experts" to theirs. Well, they are not experts. They are not even at the level of informed amateurs. But they have the power. What would you do? Sure, there are good companies and you can switch until you find one but let's recognize that statistically speaking this absolutely d…
>>>How? Programmers don't have executive powers. The secret is - and this is wielded a million times a day in a million small ways - of course we do. Lots of people do in lots of jobs, whether intended or not. You just do the thing . You don't ask about doing the thing, you don't put in a project planning proposal, you don't beg your manager to devote 20% of your time to the thing, you just go and do it because you p…
I do this so regularly it is kind of a second nature to me. Sometimes is backfires, but if you really know what you are doing, mostly you will be fine. Might even get rewarded or promoted.