The Pilot, Not the Ship
People keep asking whether AI is going to replace engineers. Wrong frame. The question is who's flying.
I design the system — the boundaries, the data flow, the failure modes, the contracts between services. That's the part that stays mine. The AI handles the keystrokes: scaffolding, boilerplate, the tenth variation of a CRUD endpoint.
I'm the pilot. The AI is the ship. Full thrust with no hand on the helm still flies you into a star.
What stays human
- Architecture. Where the seams go, what's allowed to fail, what must never.
- Scope discipline. Knowing what not to build is most of the job.
- Judgement. Reading a tradeoff the model can't feel the weight of.
What I delegate
- Repetitive implementation against a clear spec.
- First-draft tests and migrations.
- Refactors with a well-defined target shape.
The result isn't "less engineering." It's engineering with the tedious 70% compressed, so the 30% that actually decides whether a system survives contact with reality gets all the attention.
That's the whole game.
Any missing briefing before you fly? Bring me the system and we will scope the mission together.