There's nothing wrong with asking algorithm and data structure questions in an interview if the employer calls for it.

If you're hiring a junior and/or you desperately need workers, then you can lower the bar, but if you want to be picky, then asking them leetcode-tier coding questions is fine.

THERE'S NOTHING WRONG WITH ASKING A SOFTWARE ENGINEER CANDIDATE DATA STRUCTURES AND ALGORITHM QUESTIONS

If they complain that asking ds&a questions is unfair for a position where all they're going to do is shit-tier frontend work, then blacklist them for 10 years.

If people argue that Doctors don't get asked chemistry and biology questions for interviews, tell them it's because medicine is much more regulated than software and that doctors are vetted technically even before they're allowed to go job hunting. Since software doesn't have the same regulations medicine does, employers have to do the technical vetting themselves.

If you think it's unfair to ask software engineering questions to a candidate applying for a software engineering job, then find a different career.

Indian developers in the US are far better than the ones in India.

Most developers are morons, pt 3

In this post, we'll discuss the top 13.6% of developers.

You might think, after reading the previous two posts, that I'm going to be praise these developers, or even claim to be in this cohort myself.

However, things aren't so black and white.

I've worked with many developers who are much smarter and more talented than me, and I can say safely say that about 90% of them are people I'd never want to associate with again.

These developers are usually on the spectrum and have amazing tech intelligence, but little emotional intelligence. Their people skills are minimal and they usually loathe having to work with other people. While they have dozens of algorithms and data structures memorized, their social skills only include rudeness and toxicity.

This only goes to show a lesson we all eventually learn: you can be the smartest person in the world, but if you're incapable of working with or understanding other people, you aren't getting anywhere. If you're an introvert, you've got an even harder job.

Most developers are morons, pt 2

In my last post on this topic, I discussed zombie developers, i.e. lower tier developers who enter the industry from a non-tech background usually through a bootcamp or get hired at a small (and usually desperate) company after doing a few github projects.

In this post I'll be talking about the middle 67% of developers. The average joes. The ones who know enough software to build apps, maybe even publish it and sometimes (not always) actually get users using their products, even for a brief moment of time.

For these people, software is genuinely interesting to them, but they don't really put in enough effort to get good at it. They don't put in enough late nights. They don't cancel enough leisure or social events. For most, they're only good enough to not get fired (job security) and that's as far as they want to take their careers.

And I suppose there's nothing wrong with that. Most people don't have a yearning to go above and beyond, so I'd expect most developers to follow this pattern as well.

So to you, I say thank you. Thank you for doing all the boring menial work no one cares to do. You might even get a pat on the back if you put in the extra effort.

Most developers are morons.

Because the field of software development has a relatively low barrier of entry, we naturally have a large and steady supply of under-trained and clueless keyboard monkeys, hereby referred to as zombies.

The reason the industry is set up this way is because companies need a steady supply of new talent. Big Tech is so greedy, they snatch most good talent and bench them, leaving the scraps for everyone else. Other companies lower their standards and hire anybody that can copy and paste. Most entry-level software work at smaller companies is usually low risk and high churn and that's where the low barrier of entry comes in.

I have nothing against zombie developers, so long as they know their place.

I've seen too many zombies think they're CTO material after 2 years of fixing javascript bugs, or think that if they watch just enough egghead.io videos, they'll be promoted to senior.

Typically a zombie developer will go down one of two paths: 1) they either burn out and realize that software isn't what they're meant for (most common scenario) or 2) they actually get good and decide to stick around.

The ones who stick around though usually do so because it hits a sweet spot for them. To them, software is:
- Interesting enough to do it for a full-time job
- Good enough at it to secure a steady job at a two-bit company
- Pays enough to pay the bills

These people don't have a deep passion for software. It's basically just a full-time hobby for them.

And I have nothing against that. The market is satisfied, they're satisfied and I'm satisfied so long as they don't start thinking that they and I are on the same level.

Know your place, zombie devs.

Please, do not "learn to code".
The industry is already filled with too many shitheads who think they're the next bill gates.
Most people have no business coding anything.
You might hear big tech screeching about "tech shortages" and that "we need more coders" but in reality, they're trying to flood the developer market with shit-tier coders so they can pay less wages, because they're too greedy to pay their workers a decent salary.

We don't need more coders.

You're not special.

Your bootcamp project looks like dogshit and 10,000 other people wrote the same thing only better.

This website sucks. I sign up and first thing I see is a clusterfuck UI. I can't tell what's going on.
Then the morons who made the UI decided that the "new post" button was going to be on the bottom middle position.