Andrej Karpathy may have just described the future of software engineering without saying it outright.
The best AI engineers aren't becoming better at prompting.
They're becoming better at building systems around AI agents.
The biggest takeaway wasn't:
"Claude can code."
It was:
LLMs perform dramatically better when they operate inside disciplined workflows.
That's why files like CLAUDE.md are appearing everywhere.
They're not prompts.
They're operating manuals for AI agents.
Karpathy highlighted some of the biggest failure modes of AI coding:
• Models assume instead of asking.
• They overengineer simple solutions.
• They hide uncertainty.
• They modify unrelated code.
• They optimize for completion instead of correctness.
So developers started changing the game.
They encoded principles directly into the workflow:
→ Think before coding.
→ Prefer simplicity over complexity.
→ Make surgical changes only.
→ Stay focused on the goal.
→ Verify before declaring success.
And something remarkable happened.
Developers started running multiple AI agents in parallel, almost like engineering teams:
• One agent researches.
• One debugs.
• One writes tests.
• One optimizes performance.
• One validates outputs.
This isn't AI assistance anymore.
This is AI orchestration.
Then came the idea that changes everything:
"Don't tell the model exactly what to do. Give it goals, constraints, tests, and let it iterate until it succeeds."
The shift is subtle but profound.
From:
"Write this function."
To:
"Here's the objective, the constraints, the evaluation criteria, and the tests. Keep improving until it's correct."
That's a completely different way of building software.
Many developers have quietly gone from:
80% manual coding
⬇️
80% agent-driven coding
Not because AI became perfect.
Because the leverage became too powerful to ignore.
The next generation of great engineers may not be the ones who write the most code.
They may be the ones who design the best systems where humans and AI agents work together to get things done.