The Best Engineers I Know Don’t Write Code Anymore
The best engineers I know don’t write code anymore.
They write specs. They review outputs. They validate against requirements.
The code gets written but just not by their hands. And they’re shipping faster than ever.
The Identity Crisis No One Talks About
If you’re using AI to code and feel like a fraud, this post is for you.
I get it. You spent years getting good at this. Syntax, patterns, debugging at 2am — that was the craft. And now some chatbot writes a functional component in twelve seconds while you watch.
So what are you now? A copy-paste monkey? A prompt jockey?
Here’s the reframe that changed everything for me: You were never a “coder.” You were always a builder who happened to code.
The code was never the point. The product was. The solution was. Code was just the implementation layer — the most time-consuming, mechanical part of the job.
AI just took that part off your plate.
“But AI Code Is Garbage”
Yeah, sometimes. It misses requirements. It declares victory when it clearly hasn’t. It hallucinates entire functions that don’t work.
I’m not pretending otherwise.
But here’s what I stopped doing: throwing my hands up and going back to manual coding.
Instead, I fixed the system around it.
I write better specs upfront — detailed enough that AI can reference them on every pass. I use validation loops so AI can check its own work against real tests. I treat AI like a junior dev with infinite energy and zero memory: give clear instructions, verify the output, iterate.
The method is simple: spec-driven, iterative, verifiable. Write a detailed plan. Let AI take multiple passes at it. Define “done” in terms a machine can check — tests passing, types valid, linting clean.
AI doesn’t need to nail it on the first try. It needs to keep going until the spec is fulfilled. (I wrote a deeper breakdown of this system here.)
The Washing Machine Moment
When washing machines arrived, nobody asked “but what’s a mom’s value if she’s not hand-washing clothes?”
She had time for her kids now.
Same energy for devs clinging to hand-written code as a badge of honor.
The question isn’t “what’s my value if I’m not typing functions?” It’s: what can I now focus on that I couldn’t before?
Architecture. Systems design. Product thinking. The non-coding parts that actually differentiate great engineers — design sense, user empathy, knowing what to build in the first place.
Google’s been around for decades, and most people still can’t find answers themselves. Better AI tools don’t mean everyone suddenly becomes an engineer shipping products. The leverage goes to people who know what to build and why.
That’s you. If you’re reading this, you have context and taste that AI doesn’t.
Who Should Actually Worry?
Not the devs adapting. Not the ones expanding their scope into product, design, architecture.
The ones in trouble are those still measuring their worth by lines of code written by hand.
That metric is dead. Let it go.
Your job now is to be the bottleneck for decisions, not keystrokes. To spec the right thing, validate the output, and ship.
The best engineers I know figured this out months ago. They’re not mass-producing code themselves anymore. They’re directing it, reviewing it, and shipping faster than anyone still typing every semicolon by hand.
So…What Are You Building?
If you’ve embraced AI and started shipping things that were impossible before, I want to hear about it.
What are you building now that you couldn’t six months ago?
Comments