AI won't replace engineers
AI won't replace engineers. It'll replace engineers who can't use AI. Different thing.
I ship 5-10x more code than I did two years ago. Not because AI writes it all — because AI handles the mechanical parts while I focus on decisions. Architecture, tradeoffs, user needs, failure modes. The stuff that requires judgment.
The engineers who refuse to use AI tools aren't being principled. They're being slow. The engineers who copy-paste AI output without reading it aren't being productive. They're creating debt.
The skill that matters is knowing what to ask for, evaluating whether the output is correct, and understanding the system well enough to catch when the AI is confidently wrong. That's not "using AI." That's engineering with a better tool.
A carpenter isn't threatened by a power drill. They're threatened by a carpenter with a power drill who's faster and just as precise. Same thing here. Learn the tools. Apply the judgment. Ship more.
More in Thoughts
Remote work is a skill
Working across Japan, USA, and India taught me that async communication is everything.
Model size is a vanity metric
Ran Kokoro-82M on my MacBook for TTS. 337MB. Broadcast-quality speech. Zero cost.
The best code is no code
Before writing a function, check if a library does it. Before a library, check if you need it at all.