In my previous article, I argued that AI is just the next abstraction layer — the same pattern we’ve seen a dozen times in software history. Each layer demands a new skill. So what does the AI layer demand?
I think the answer is hiding in plain sight. And some very powerful people just demonstrated it.
Something Interesting Happened Recently
Mark Zuckerberg started coding again after a 20-year break. According to multiple reports, he moved his desk to Meta’s AI lab, spends 5 to 10 hours a week writing code, and is “coding all day long” alongside the Meta Superintelligence Labs team. The man who built Facebook in a dorm room and then spent two decades managing tens of thousands of people — is shipping diffs again.
Garry Tan, CEO of Y Combinator, returned to coding after 15 years using AI tools like Claude Code. He described himself as “addicted” to it, sleeping four hours a night because he couldn’t stop building things.
Sergey Brin, Google’s co-founder who stepped back from day-to-day operations years ago, came out of retirement to code on Gemini. He’s reportedly assembling an elite “coding strike team” and is directly involved in hands-on development.
And there’s a quote from The New Stack that captures this perfectly: executives are building with AI because they were “tired of explaining it to somebody who was supposed to build it for me.”
Why is this happening? These people haven’t written production code in over a decade. What changed?
The Career Ladder Was Always About Communication
Let’s take a step back. The most common career paths for a developer are either the strict technical way — from developer to tech lead, then architect — or the management way — team lead, then head of engineering, CTO.
In both ways you start from doing things yourself and gradually move to teaching — or better to say, guiding — others how to do it. Or strictly overseeing the whole process. You stop writing code and start writing explanations. You stop implementing and start reviewing. You stop building and start describing what needs to be built.
A senior architect doesn’t write code. They write ADRs, design documents, system diagrams. They explain to teams what to build and why. A CTO doesn’t push commits. They articulate technical vision so clearly that hundreds of engineers can execute on it independently.
The higher you go — the more your job becomes pure communication of technical intent.
Sound familiar?
My Theory: The Explanation Bottleneck Is Gone
My theory is simple. People who know how to explain to others what and how they exactly want to do — can now skip the extra step of explanation and do things directly. Faster. Without the telephone game of requirements passing through three layers of interpretation.
Think about it. A CTO who spent years learning to articulate technical vision clearly, who mastered the art of describing systems and behaviors — that person now has a tool that actually understands those descriptions and turns them into working code. The skill they developed for managing people turned out to be the exact skill needed for managing AI.
The bottleneck was never their inability to code. It was the cost of translating their vision through other people. AI removed that cost.
That’s why Zuckerberg is coding again. Not because he suddenly remembered C++ syntax. But because he spent 20 years perfecting the skill of explaining what he wants — and now there’s a tool that listens.
Why This Should Concern Mid-Level Developers
Here’s the uncomfortable part. If the key skill for working with AI is the ability to articulate technical intent clearly and precisely — then the people who are best at it are not junior developers. They’re not even senior developers who spent their careers heads-down in code.
They’re the people who spent years learning to communicate technical ideas to other humans. Tech leads. Architects. Engineering managers. The people who already climbed the ladder.
This doesn’t mean mid-level developers are doomed. It means the skill you need to develop is not “learn more frameworks” or “memorize more APIs.” It’s the skill of clear technical communication. The ability to describe what you want, why you want it, what constraints exist, and what “done” looks like.
This is not “prompt engineering” as some buzzword. This is the same skill that makes great tech leads, great architects, great CTOs — the ability to articulate technical intent clearly and precisely.
The Skill That Compounds
Here’s the good news. Unlike memorizing API signatures or framework quirks — communication skill compounds. It doesn’t deprecate with the next major version release. It doesn’t become obsolete when a new framework appears.
A developer who can clearly explain a system’s architecture, articulate trade-offs, and describe desired behavior precisely — that developer will be effective with whatever AI tool comes next. Because the tools will only get better at understanding us. The bottleneck will always be our ability to express what we mean.
What This Means Practically
If you’re a developer reading this and thinking “okay, but what do I actually do?” — I have a concrete answer for that. In the next article, I’ll break down exactly how AI agent workflows mirror the workflows we already use in human teams, and how you can leverage that understanding to work with AI dramatically more effectively.
Spoiler: if you’ve ever written a good Jira ticket, you’re already halfway there.
Top comments (0)