The Moat Shifts to Judgment
Syntax fluency was never the real moat, but it used to matter a lot. Knowing the language well, knowing the framework, knowing how to structure a solution quickly. These created real differences between engineers. AI is collapsing those differences fast. What's left is harder to learn and harder to fake.
Judgment. Knowing what to build, knowing when something's wrong, knowing when to stop. Taste, in the design sense: an internalized sense of what good looks like that operates faster than explicit reasoning.
David Hume argued in 1757 that taste isn't a fixed trait or innate gift. It's a faculty, developed through practice, sharpened by comparison, and refined by honest reckoning with the gap between what you thought was good and what turned out to be. That's a useful frame for engineering too. The senior engineer's judgment isn't mystical. It's accumulated. It took years of building things, breaking them, and paying attention to what failed and why.
There's a split developing in engineering culture worth naming. On one side are what you might call Experimenters: developers who've leaned into AI tooling aggressively, automated as much as possible, and are shipping faster than they ever did. On the other are Guardians: developers who believe understanding code at a fundamental level is non-negotiable, who worry about correctness and maintainability, and who are skeptical of output they didn't trace through themselves.
Both are partially right. Experimenters are correct that speed matters and the tooling is genuinely powerful. Guardians are correct that fast output without understanding produces systems that are fragile, expensive to maintain, and difficult to hand off.
The prediction that Experimenters will win because technology trends toward convenience misses what happens after you ship. Software evolves. Someone has to maintain it, debug it, extend it in ways nobody anticipated. The Guardian's concern isn't abstract. It's a description of what happens two years after the Experimenter ships and moves on.
There's also something the Guardians are protecting that they don't always have words for. Graham Wallas described creative work as having four stages: preparation, incubation, illumination, verification. Incubation is the slow, largely unconscious phase where exposure becomes understanding and understanding becomes judgment. AI collapses that timeline. When you skip it, you don't eliminate the need for judgment. You expose its absence faster. Guardians are instinctively resisting that collapse. The instinct is right even when the reasoning isn't fully articulated.
The engineers building durable careers aren't choosing between these postures. They're learning to hold both.
The disciplines that compound at senior levels haven't changed much, but their relative weight has. Technical skill is still required. What's changed is that it's no longer sufficient on its own.
Product thinking (knowing what's worth building) is harder to acquire than coding ability and more valuable at the margin. Project execution (making sure things actually ship) is underrated in technical culture. People skills, the ability to influence, align, and develop others, have always separated the engineers who advance from the ones who don't.
The biggest gains come from combining these. An engineer who can write excellent code, articulate what the customer actually needs, drive a project through ambiguity, and bring a team along isn't competing on syntax. They never really were.
There's a version of this that gets stated as "the moat is soft skills now" and that framing is wrong. The technical foundation still matters. What's changed is that technical skill is increasingly table stakes, and differentiation happens above it.
One useful analogy: anyone can buy chocolate-making equipment and start a brand today. The ingredients are commoditized, the manufacturing is understood. What Hershey's and Lindt have isn't better cocoa. It's distribution, brand trust, and decades of understanding what makes someone reach for one bar over another. Software is moving toward the same dynamic. The winners won't be the best implementors. They'll be the teams that understood their users better, got there first, and built something people felt attached to.
If someone could generate the implementation for you in an afternoon, what would you still be the best person in the room to contribute? That's the moat.
In a world where everyone has access to the same generative tools, the differentiator isn't what you can produce. It's what you can see.
Part 9 of 14 — What I Think About AI Engineering**