My developer skills are still important. Despite AI.
Right now a particular kind of engineer is going quietly defensive.
The ones most proud of the craft. The ones who always had opinions about patterns, layers, seams, and tradeoffs. The ones who built their identity around knowing how software is really made.
You can hear it. “Vibe coding, no way.” “People don’t understand what they ship.” “Wait until it hits production.”
Some of that is true. Most of it is defensive posture.
And the defensive posture is a tell.
The Artisan Trap
The engineers most defensive right now remind me of a very specific kind of cook.
The one with fifty knives.
Damascus steel. Damast. Hand-forged. Ebony handles. A rack for every occasion, a pocket on the apron for every blade.
Beautiful knives.
No dinner.
The knives were never the point. The meal was.
You don’t need fifty knives to cook well. You need four workhorses and the willingness to actually cook.
Same in software. You don’t need a cathedral of patterns to ship well. You need enough judgment to know what holds, what breaks, what’s worth paying for — and then you ship.
If your craft doesn’t produce a working thing that people use, it’s not craft. It’s a hobby with good lighting.
What AI Actually Killed
Not craft. Not architecture. Not judgment.
The translation layer.
The old world needed a lot of engineers whose job was: take intent, translate it into working code, ship it. Middle-weight implementation. Instructions in, code out.
That layer compressed. Hard.
Not because understanding software is suddenly worthless. Because pure translation from intent to implementation got cheap.
This is the part that is confusing people. It looks like the whole craft is being devalued. It is not. One specific layer inside the craft got automated. The rest got more important, not less.
The Difference AI Makes Visible
Two things are being built in parallel right now.
One is a zoo of vibe-coded apps. They demo well. They help people — short-term. They have gaps that only show once usage grows, once the data gets messy, or once requirements shift. Nobody can tell you where the boundaries are, why this service exists, or what the fifth iteration will do to the structure.
The other is real software. Solid, shaped, understandable, evolvable. The kind of thing that still makes sense six months later when the constraints change. The kind of thing you can migrate, extend, or cut apart without the whole structure going sideways.
Both look similar at demo time. They diverge under load.
What decides which one you end up with is not how much code got generated. It is whether someone with solid technical judgment shaped the system — and whether that person also understood what the product was actually for.
Why Both Sides Matter Now
Tech without business gives you architecture astronauts. Beautiful systems. No users.
Business without tech gives you the vibe-coded zoo. Fast demos. Nothing that holds.
The people with disproportionate leverage right now are the ones who operate across both. They make the architectural calls that keep software alive, and they stay connected to why the software exists in the first place.
That is not a new skill. It is an old skill that just got visibly more valuable.
Before AI, this kind of engineer was quietly faster than everyone around them.
Now it is not quiet anymore.
Stop Confusing Craft With Ritual
If you care about the craft, this is not the moment to go defensive.
This is the moment to stop confusing the craft with the ritual around it.
The craft is: building software that works, holds, scales, and serves the point of the product.
The ritual is: patterns for patterns’ sake, layers for layers’ sake, knives you never cut with.
AI is ruthless about the ritual. It exposes it.
It does not touch the craft.
If anything, it finally shows the craft for what it always was — the thing that separates a working product from a pile of generated code.
My Skills Compound Now
They always were important. The difference now is that the gap shows up faster.
If you build solid software and understand the business, this is your moment. Your decisions compound harder than they ever did, because execution no longer slows you down.
If you do not yet, the answer is not panic. It is also not defensive gatekeeping.
The answer is growth. Engineers toward the business. POs and managers toward the tech. Both directions. Both honest about how many layers deep the other side actually goes.
And for the artisans:
Put down some of the knives.
Cook.