The End of Coding as We Know It
Spotify's CEO dropped a bombshell: their best developers haven't written a single line of code in months. Here's what that means for the rest of us.
The End of Coding as We Know It
Last week, Spotify's CEO dropped a bombshell that should make every software developer pause: their top engineers haven't written a single line of code since December. They're not alone — they're the best at what they do, and they're now purely "supervising" AI-generated code.
This isn't a dystopian hypothetical. It's happening now.
The New Reality
During Spotify's Q4 earnings call, Gustav Söderström explained that the company's most senior engineers have shifted entirely to what you might call "AI orchestration." They prompt, they review, they refine — but they don't type syntax anymore.
Think about that for a moment. These are the people who presumably knew how to build things from scratch. They understood algorithms, memory management, edge cases. Now? They're prompts engineers.
The math is simple: AI writes code faster, cheaper, and — here's the uncomfortable part — often better than junior developers. Why would a company pay someone to do slowly what an LLM does in seconds?
Why This Matters
This isn't just about Spotify. It's a signal of where the entire industry is heading.
Three years ago, "vibe coding" — building apps by describing what you want to an AI — was a joke. Last week, it was named Collins Dictionary's Word of the Year. Now Spotify's top talent is living that reality.
The implication is stark: if the best developers are supervising AI, what happens to the rest of the ladder? Junior developers, bootcamp graduates, CS students — where do they fit in a world where the entry-level work is automated?
The Honest Answer
Here's the thing: we don't fully know yet.
Some argue this is liberating. Developers can focus on architecture, design, and problem-solving rather than syntax. The "programming" part — the typing — becomes secondary to the thinking part.
Others see a crisis. If you never write code, how do you learn to think like a programmer? How do you debug something you didn't write? How do you improve if you've never struggled with the fundamentals?
What to Do About It
The developers who'll thrive aren't the ones who compete with AI on speed. They're the ones who understand the why behind the code — the business logic, the user needs, the system design.
Maybe it's time to stop learning "how to code" and start learning "how to solve problems with code."
The robots aren't coming for your job. They're already here. The question is: are you directing them, or are you being directed?
Updated: Testing Vercel deployment trigger
What do you think? Are we witnessing the end of programming — or just its evolution? test test 2 test 3 Vercel test no-ff test