Well, that's a long rant. Some parts are interesting, others less so.
> Job Openings vs. Interest Rates
Everyone already knows this
> Company Level to Compensation Scale
Everyone already knows that over the last 20 years employees at LASAGNAFAANG big tech companies in the US have made absurd amounts of money relative to how much skill is actually required. If you work in tech in San Francisco it must be easy to compare yourself to these people and be envious all the time. Outside of the US (or outside of tech) it's more normal to view these jobs as a weird aberration, not the norm. Why not compare yourself to public school teachers, lorry drivers, nurses, enlisted infantry soldiers, etc? Many of them could probably have earned absurd amounts in Silicon Valley too, had they been in exactly the right place at exactly the right time.
> Coding interviews
If you are failing leet code interviews and you're unemployed then why not just spend a week or two practicing leet code questions? There are some egregious examples of small companies using algorithms questions on graphs as a hazing exercise, but most places are just using easy or medium coding tests as a basic filter on people who are able to do arbitrary programming tasks whilst communicating their thought process. If you have US citizenship and enough experience to get an interview, you are already extremely lucky. Whining that getting a job also requires practicing a few coding questions because you see it as beneath you is silly.
> "We find the midwit problem in job interviews all the time where interviewers think they are “elite special evaluators” needing to gatekeep the unwashed hoards of desperate candidates, but interviewers often can’t reliably judge or measure people who have better answers than they expect"
Isn't that exactly what standard coding tests avoid? People who think they are elite special evaluators ask off-the-wall questions about particular technologies or processes, or abstract logic questions, thinking they are so clever they can infer the inner workings of the candidates mind. The low IQ and high IQ solution is to realise that as an interviewer you aren't very special, and that assessing candidates in the space of an hour or two can never be more than a very lossy, rough filter. Under these circumstances, generic coding tests aren't such a bad idea.
> Field Report: Job Experience Notes
My experience of work have been similar. That's just what it's like at the average mediocre tech job. Hence the The Daily WTF running since 2004
> "At some point, a switch flipped in the tech job market and “programmer jobs” just turned into zero-agency task-by-task roles working on other people’s ideas under other people’s priorities to accomplish other people’s goals"
> Job Openings vs. Interest Rates
Everyone already knows this
> Company Level to Compensation Scale
Everyone already knows that over the last 20 years employees at LASAGNAFAANG big tech companies in the US have made absurd amounts of money relative to how much skill is actually required. If you work in tech in San Francisco it must be easy to compare yourself to these people and be envious all the time. Outside of the US (or outside of tech) it's more normal to view these jobs as a weird aberration, not the norm. Why not compare yourself to public school teachers, lorry drivers, nurses, enlisted infantry soldiers, etc? Many of them could probably have earned absurd amounts in Silicon Valley too, had they been in exactly the right place at exactly the right time.
> Coding interviews
If you are failing leet code interviews and you're unemployed then why not just spend a week or two practicing leet code questions? There are some egregious examples of small companies using algorithms questions on graphs as a hazing exercise, but most places are just using easy or medium coding tests as a basic filter on people who are able to do arbitrary programming tasks whilst communicating their thought process. If you have US citizenship and enough experience to get an interview, you are already extremely lucky. Whining that getting a job also requires practicing a few coding questions because you see it as beneath you is silly.
> "We find the midwit problem in job interviews all the time where interviewers think they are “elite special evaluators” needing to gatekeep the unwashed hoards of desperate candidates, but interviewers often can’t reliably judge or measure people who have better answers than they expect"
Isn't that exactly what standard coding tests avoid? People who think they are elite special evaluators ask off-the-wall questions about particular technologies or processes, or abstract logic questions, thinking they are so clever they can infer the inner workings of the candidates mind. The low IQ and high IQ solution is to realise that as an interviewer you aren't very special, and that assessing candidates in the space of an hour or two can never be more than a very lossy, rough filter. Under these circumstances, generic coding tests aren't such a bad idea.
> Field Report: Job Experience Notes
My experience of work have been similar. That's just what it's like at the average mediocre tech job. Hence the The Daily WTF running since 2004
> "At some point, a switch flipped in the tech job market and “programmer jobs” just turned into zero-agency task-by-task roles working on other people’s ideas under other people’s priorities to accomplish other people’s goals"
Yup I agree it sucks, but it pays the rent.