Augmented

Where you are

You live in your editor with AI chat and autocomplete. You ask the model when stuck, accept the good suggestions. But you still write and edit the code, line by line. Your mental model is "AI helps me code." You're faster than you were a year ago, and that gain is real. It's also what makes the next jump easy to put off.

What's keeping you here

It isn't skill — it's identity and trust. You still see yourself as the person who writes the code, so handing that over feels like losing control (or losing the part of the job you love most). That's the real wall, and almost everyone is stuck at it. The irony is that the skill is already in your hands; what's missing is the willingness to stop being the one holding the keyboard.

Why it matters now

The bottleneck moved. As Thiago Ghisi puts it, the constraint isn't capacity, it's choice. Writing code got cheap; the value moved to directing and judging it. Staying here means competing on the one thing that just got commoditised. And the people who cross don't drift back. The gap between directing several agents and hand-writing one function widens every month you wait.

What's different

Writing functions becomes writing specs. Debugging your own code becomes reviewing an agent's — harder, not easier. "How do I build this?" becomes "Is this the right thing, and how do I know it's correct?" Reading your own code, you remember why every line is there; reading an agent's, you reconstruct the intent from scratch, which is a slower and more deliberate kind of attention than writing ever asked of you.

The leadership shift

Crossing is a management skill, not a coding one — that's the whole reframe. Directing an agent is delegating to a junior: set the intent, frame the constraints, judge the result, don't micromanage. The engineers crossing fastest aren't the strongest coders; they're the ones with management instincts. If you've ever mentored a junior well, you already know how — just point it at the agent.