Level 2
Crossing
You're on the far side of the cliff now — find your footing.
What's a level? How far you've shifted from writing code yourself to directing the AI that writes it — five bands, from hands-on-keyboard to running a fleet of agents. Most of us are mid-ladder, and climbing.
Where you are
You've started directing agents instead of typing the code yourself. Some days it's exhilarating, some days you grab the keyboard back the moment it gets hard. You're learning to write a spec, set the boundaries, and let something else do the building. The mental model is shifting from "AI helps me code" to "I direct work that gets coded."
What's keeping you here
The pull back into the editor. Under pressure, watching an agent take the long way round, the IC instinct screams just fix it myself. And it's faster, this once. Every time you give in, you stay a very senior IC with an agent, instead of becoming someone who directs. The wall here isn't the tool; it's learning to hold back and let the work happen a way you wouldn't have chosen.
Why it matters now
Crossing is a cliff, not a gradient. The workflow on this side doesn't look like the workflow you left, and most engineers never make the jump. You have. The risk now isn't falling off; it's drifting back. The skills you build in these first months (when to trust, when to step in) are the ones that decide whether the jump sticks. (This is the discontinuity Yegge flags at his Level 5: the one boundary in the whole ladder that's a leap, not a step.)
What's different
Delegating goes from a one-off experiment to a reflex. You stop asking "can I let the agent do this?" and start asking "what's the right brief, and how will I know it's good?" Reviewing agent output (fluent, confident, sometimes quietly wrong) becomes the core of your day, and you get better at reading for rot, not just catching crashes.
The leadership shift
This is the moment the whole thing reveals itself as a leadership transition wearing a coding costume. Directing an agent is delegation, ownership transfer, in the language of the leadership ladder: you set direction and judge the outcome, you don't control every line. Marquet's submarine crew didn't ask permission; they said "I intend to…" and brought the reasoned decision. Aim the agent at that same standard. The engineers thriving here aren't the deepest technologists — they're the ones who already learned, with people, how to delegate without micromanaging.
Your moves
- When the urge to grab the keyboard hits, pause and ask instead: what constraint was missing from my brief? Fix the brief, not the code.
- Match the leash to the risk. Tight review on the critical path; let it run free on tooling, tests, and scripts where mistakes are cheap.
- Treat a bad output as a signal about your spec, the way a good manager treats a missed deliverable as a briefing problem first.
- Run the "I intend to…" pattern: make the agent state its plan and reasoning before it builds, and judge the plan, not just the diff.
The engineers adapting fastest aren't the strongest coders. They're the ones with management instincts — they delegate without micromanaging, accept imperfect output, and iterate. You're not pair-programming with AI; you're managing it.
Next rung
Directing: directing agents stops being a thing you try and becomes the default. Specs, constraints, and reviewing output are simply how you work now — not the exception you reach for on a good day, but the shape of every day.