AI programming and the outdated programmer syndrome
Published on
“I’ve never felt this much behind as a programmer” - that was a sentence Andrej Karpathy, one of the biggest references in AI in the world, recently dropped and it made quite a lot of noise.

This end of 2025 and start of 2026 was that time of year when leadership folks have more free time to work on personal projects, and apparently, all of them dove into coding agents.
Besides Karpathy’s, two other examples that circulated a lot were David Holz’s (founder of Midjourney, ex-NASA) saying he managed to do more personal projects during this end-of-year vacation than in the last 10 years; and Jaana Dogan’s (Principal Engineer at Google), commenting that Claude Code generated in one hour a distributed system prototype that her team had been trying to align on and build for a year.


This made me reflect over the last few days and have conversations with some of the smartest people I know. The first natural reaction is skepticism: was Jaana’s team bad? Or is comparing an AI prototype with a complex legacy system unfair?
Both things can be true, but speaking from my own experience and from reports of close friends over the last 2-3 months, these examples have started to multiply. I’m hearing from SEVERAL very experienced Devs I trust about real cases of demands that would take 1 month being delivered in 1 week, a 4x efficiency gain.
Then there’s an interesting paradox that one of those friends brought up: if productivity in writing code went up 4x, why aren’t we seeing Apple, Google or Microsoft launching 4x more software or features?
The conclusion I reach with these points might be painful for the more ‘roots’ crowd, but I think not so much for more experienced leaders: writing lines of code is definitely not the bottleneck of digital products. The real bottleneck is product definition, requirements alignment and, above all, deciding what to build.
One of those friends dropped a line that really got me (I swear it’s not fanfic): “I’m already seeing this on my team. The Dev who works only as a ‘code typist’ is turning into almost a luxury typist, and is already starting to flounder. The Dev with a ‘product mindset’, who understands the business, is flying in here.”.
And I’ll add: seeing the evolution of tools like Replit, Lovable and others, even product people who aren’t developers are already managing to create prototypes at a speed that was impossible until recently.
For Devs, I believe the standard in Brazil has been Cursor + Claude Opus 4.5. In the US, I practically only hear about Claude Code.
At the end of the day, you can conclude that the technical barrier went down, but the responsibility of choosing the right solution went up.
Here’s a sincere question: has this 4x acceleration already reached your team or does it still seem far away?