Don't Delegate the Thinking
The pull to hand everything over is real. Tools are capable enough now that you can get something that looks like a complete answer on almost any problem, fast. Reaching for that feels like the efficient choice.
The problem is that fluent output looks like thinking. It reads like a decision was made. But the model didn't decide anything. It generated the most probable continuation of your prompt. The judgment that should have happened before that output didn't happen. It got skipped.
Ted Chiang wrote about this in a different context. He was talking about writing, but the observation transfers: your first draft isn't an unoriginal idea expressed clearly. It's an original idea expressed poorly, and it's accompanied by your dissatisfaction — your awareness of the gap between what it says and what you wanted it to say. That dissatisfaction is doing real work. It's the signal that drives revision.
When you start with text a model generated, that dissatisfaction is gone. You're editing, not thinking. You're reacting to what's in front of you rather than working from an intention that was yours to begin with.
The same thing happens with architecture decisions, system design, and technical tradeoffs. If the model makes those calls and you review the output, you're not the author of the decision. You're the approver. Those are different jobs, and only one of them builds judgment over time.
There's plenty worth delegating: drafting, scaffolding, boilerplate, repetition, the parts of implementation that are mechanical once you know what you want. AI compresses those meaningfully, and the compression is real.
What's worth keeping: the thinking that happens before any of that. What should this system do? What are the constraints? What does good look like here? What am I willing to be responsible for? Those questions have to be yours, answered before the model gets involved. Otherwise you're not engineering. You're supervising.
My operating principle, stated plainly: delegate the expression, keep the thinking. Let AI handle the scaffolding of ideas I've already formed. Use it to move faster on decisions I've already made. When I notice I'm reaching for it because I don't want to think through something hard, that's the sign to close the chat window and think it through.
The developers getting the most out of these tools aren't the ones offloading the most. They're the ones who've figured out which parts of their work are genuinely mechanical and which parts require them specifically, and they're protecting the second category.
Part 11 of 14 — What I Think About AI Engineering**
← Three Things I Keep Coming Back To Vibe Coding Is Real, But Vibe Thinking Isn't →