Loading...
Loading...

Jensen Huang said kids shouldn't learn to code. Anthropic predicted 90% AI-written code by 2025. BLS says developer jobs grew 3.8%. Let's talk about what actually happened.
Remember 2024? Every tech CEO had a hot take about developers going extinct. Jensen Huang told a room full of people that kids shouldn't bother learning to code. Anthropic's Dario Amodei predicted that 90% of code would be AI-written within months. Sam Altman casually mentioned that GPT-5 would make junior developers "unnecessary."
I saved screenshots. Because I had a feeling I'd want receipts.
Fast forward to 2026. Let's look at the actual numbers instead of keynote vibes:
| Metric | Prediction | Reality (2026) |
|---|---|---|
| Developer job growth | "Near zero" — Jensen Huang | 3.8% growth — BLS |
| AI-written production code | "90% by 2025" — Anthropic | ~15-25% (with human review) |
| Junior dev hiring | "Eliminated" — various VCs | Down 17% but NOT eliminated |
| Developer salaries | "Cratering" — Twitter pundits | Up 4.2% median — Stack Overflow Survey |
| Total developers globally | "Shrinking" — doom articles | 28.7M and growing — SlashData |
That's... not the apocalypse they sold us. 😅
Here's what non-engineers don't understand: writing code is maybe 20% of software development. The rest is:
AI is genuinely great at generating boilerplate. It's terrible at asking "wait, should we even build this?" 🧠
This is the part nobody predicted. When you make software cheaper and faster to build, you don't get fewer developers. You get more software. Companies that couldn't afford custom tools now want them. Startups that needed 10 engineers can ship with 4 — but there are 3x more startups.
The Jevons Paradox strikes again. Making something more efficient increases total consumption.
I use AI coding tools daily. Copilot, Claude Code, Cursor — the whole stack. And here's what I've learned: AI-generated code works great for the happy path. But production software isn't the happy path. It's edge cases, error handling, security vulnerabilities, and that weird race condition that only appears under load.
Every week I see a PR where someone clearly let AI write the code and didn't review it carefully. The bugs are subtle and expensive.
Let's be honest about what DID shift:
| Before AI Tools | After AI Tools |
|---|---|
| Write CRUD endpoints manually | Review AI-generated endpoints, fix edge cases |
| Google Stack Overflow for syntax | Prompt AI, validate the output |
| Spend 2 hours on boilerplate | Spend 2 hours on architecture decisions |
| Junior devs learn by writing code | Junior devs learn by reviewing AI code |
| "Typing speed" as a joke metric | Actually less typing, more thinking |
The real productivity gain from AI tools? Somewhere between 1.3x to 2x for experienced developers. Not the "10x" that VCs promised. And for junior developers? Often slower, because they can't evaluate whether the AI output is correct.
GitHub's own study found that Copilot users completed tasks 55% faster — but only the tasks that were well-defined and isolated. Real-world engineering is neither.
AI made great developers more productive and mediocre developers more dangerous.
If you deeply understand software architecture, system design, and debugging — AI tools are incredible force multipliers. You can ship at 2x speed because you know which AI suggestions to accept and which to reject.
If you don't have that foundation? You're shipping bugs faster. And you can't tell the difference.
The developers who thrive won't be the ones who resist AI tools. And they won't be the ones who blindly trust them. They'll be the ones who use AI as a tool while maintaining the judgment to know when it's wrong.
Jensen Huang was wrong. The kids should absolutely learn to code. In fact, understanding code is more important now because someone needs to verify what the AI generates.
The doomsday predictions about developer jobs were driven by keynote hype, VC narratives, and people who've never actually shipped production software. The data tells a different story.
Developers aren't going extinct. The job is changing. And honestly? It's more interesting now than it was three years ago. 🚀
Save this post. I want receipts when the next round of "developers are dead" predictions drop in 2027.
Implementation roles dropped 17%. AI writes the boilerplate now. But 28.7M developers globally still need to come from somewhere. Here's what the new junior dev looks like.
GitHub's own data confirms it: more than half of all code on the platform is now AI-generated. This isn't a future prediction — it's happening RIGHT NOW. Here's what it means for your career and what skills actually matter.
Will AI replace developers? Which skills matter in 5 years? How should you adapt your career? An honest perspective from someone building with AI daily.