Some of the best engineers I know have not touched a coding agent. They tried the tools, disliked what came out, and closed the tab. The industry has a category waiting for them: laggards, dinosaurs, the people who scoffed at compilers and source control and were wrong both times. Underneath the name-calling, the holdouts are asking a quieter question than “how do I catch up?” They want to know whether there’s still a place for someone who loves the work itself.
There is, and it takes no wishful thinking to make the case. Mechanization has come for a craft before. The branch with the future in it belonged to the craftsmen who made the machine their material, and the people who loved the work were its founders, not its casualties.
The refusal is made of the thing that survives #
Ask a holdout why they don’t use the tools and you rarely hear “I can’t learn this.” You hear four complaints. The code looks right but isn’t, which is more dangerous than obviously wrong, because it’s engineered to get past your review. Checking it feels like grading a confident student who didn’t do the reading: fluent prose, no understanding underneath, all the real work pushed onto the grader. The workflow is worse than the old one: you used to hold the whole problem in your head and work it; now you type a request, wait, and pull the lever again when the answer disappoints. And the code that comes back often works without being good. It passes the tests while making the system harder to live in, and the tools can’t tell the difference.
Every one of those is a quality objection. You cannot be offended by slop without a working definition of good, and a working definition of good is the rarest asset in the transition. Over the next decade the craft itself (writing the code) gets embedded into the machine, the way weaving was embedded into the power loom. What that leaves for humans is the layer above: specify the work, judge the output, handle the exceptions, own the consequences. The engineers refusing the tools on taste grounds are not disqualified from that future. They are walking around with its scarcest input.
Managers have seen this before. The hardest person to promote is the best craftsman on the floor, because their standards make delegation painful: every handoff is a small grief about how they’d have done it. But nobody ever concluded that their standards made them unfit to supervise. The standards were the qualification, and the pain was just the price.
Craft doesn’t die under mechanization. It splits. #
Between 1790 and 1850, skilled artisans met three different fates.
Tend the machine. The handloom weavers who kept weaving rode their wages down for forty years. This is the deskilling everyone fears, and it was real: the craft decomposed into machine-minding, at machine tempo, at machine wages. But tending with standards was a different job. The cotton mule spinners ran machines all day and still kept authority over quality, set the pace of the room, and became the best-paid workers on the floor. When the steam press made print cheap and endless, publishing invented the editor; Maxwell Perkins never wrote a novel, and Fitzgerald and Hemingway are hard to imagine without him. Agent-era review works the same way. At the generator’s pace, with standards sanded down to “does it pass CI,” it’s the weaver’s fate — the holdouts are right to refuse that. With the standing to say “this does not ship,” it’s the spinner’s job, or the editor’s. The machines never retired the craftsman’s eye. They raised its price.
Retreat to the boutique. William Morris watched industrial goods flood England and built the Arts and Crafts movement in protest: honest materials, hand work, the whole task in one pair of hands. The results were beautiful and the economics were damning. Morris despaired that he was spending his life “ministering to the swinish luxury of the rich,” because handmade was now, by definition, what only the rich could buy. A century later the quartz crisis ran the same experiment on Swiss watchmakers: roughly two-thirds of the industry’s jobs gone in fifteen years, then a renaissance in which the mechanical watch came back as a luxury object, the craft more prestigious than ever at a fraction of its former size. Hand-written code will have this market. Safety-critical firmware, cryptographic kernels, the hot path, code where a human name on every line is the product. Prestigious, real, and small — a destination for some, not an answer for a profession.
Turn and face the machine. The millwright was the master craftsman of the pre-industrial world — carpenter, mason, smith, and hydraulic engineer in one trade, who could build a mill from the dam to the gear teeth and understood the whole of it. When steam arrived, the millwrights mostly didn’t tend the new machines. They built them. William Fairbairn, apprenticed millwright, became one of the great engineers of the century and wrote that the millwright had been the general engineer before the title existed. John Smeaton, who trained making scientific instruments, was the first man to call himself a civil engineer. James Watt was an instrument maker at Glasgow when the university handed him its broken model of a Newcomen engine. The Institution of Mechanical Engineers was founded in 1847; its first president was George Stephenson, a colliery engine-man who couldn’t read until he was eighteen.
Engineering is not the craft the Industrial Revolution destroyed. It is the craft the Industrial Revolution created, staffed by craftsmen who walked toward the machine carrying their standards. Software engineering now sits where weaving sat in 1810: a young craft whose production layer is being embedded in capital equipment. The third path just reopened. It doesn’t have a name yet, and that is the opportunity: last time, the people who took it got to define what the profession was.
The anatomy of the new craft #
So what is the new craft? Start with what it isn’t: prompting. “Prompt engineering” is to the new craft what pulling the power-loom lever was to weaving.
When machines took over sawing, fine woodworking didn’t disappear; sawing as a livelihood did. Walk into a serious furniture maker’s shop today: the table saw does the stock removal, and the chisels come out where the tolerances live. Nobody calls the table saw a betrayal of the craft. The craft reorganized around the parts machines are bad at, and the standards migrated to the joints.
The joints of software are already visible. Problem definition — deciding what to build, and the harder discipline of what not to. Invariants and interfaces, the decisions every agent downstream inherits, where one lazy choice spreads across a fleet’s output. Verification, which asks not “does it pass” but “is it true,” the difference the holdouts already care about more than anyone. And reading, which becomes the primary hand skill of the new craft: the mule spinner’s walk down the line, eyes on the threads. The engineers who can read code the way an editor reads prose, fast and suspicious and feeling for the soft spots, hold the skill everything else depends on.
An agent is leverage on judgment, and leverage multiplies whatever it’s applied to, including nothing. The person who skipped the craft and went straight to directing fleets has nothing for the fleet to multiply. You, meanwhile, have been rehearsing this job for years: every pull request you reviewed, every design doc you tore apart, every junior you taught what good looks like, every time you explained why the working code was still wrong. The senior craftsman’s secondary skills just became primary.
The obvious objection: won’t the machine learn the joints too? Some of them, probably. But two things resist. The first is accountability. When an agent ships a security hole, the org chart still needs a human name attached to the failure, and the name has to belong to someone whose judgment you trust. Responsibility doesn’t compile. The second is formation. Taste is built by reps of making; you develop the eye by cutting a thousand bad joints yourself and living with them. Which points at the transition’s hard problem: the apprenticeship pipeline that manufactures taste is eroding, as juniors learn to delegate before they’ve learned to make. The industry will have to rebuild formation deliberately, the way medicine did with residency, and it will probably do so late. But for the engineer whose taste is already formed, the implication is impolite and true: the market is about to stop manufacturing the thing you already have. Scarce assets appreciate.
The cottage comes back #
Before the factory, the weaver owned the whole task. His pace, his tools, his standards, his cottage. The factory’s deepest wound went beyond wages: it decomposed the work. The task shattered into fragments, each assigned to a different pair of hands, and afterward almost nobody in the industrial economy owned a whole thing again. Software inherited the fragment. The team became the unit of work for the same reason the factory floor did: no single person could hold the whole system. Conway’s law is the cottage’s tombstone.
This mechanization runs the film backwards. One craftsman directing a fleet can own a whole thing again — conceive it, design it, build it, ship it, answer for it — at a scale that used to take a floor of people. The solo project that was always five years of nights and weekends is now a season. The system you’ve carried in your head for a decade, the one that never survived contact with a roadmap, is buildable now, by you, to your standards, with your name on it.
I won’t pretend nothing is lost. Some of the love really was the flow state, hands on the material, and that changes; a craftsman is allowed to grieve a tool. But be honest about the object of the love. No weaver loved the shuttle. He loved the cloth, and the shuttle was the toll between him and it. So with us: the love was the problem, the design, the standards, the moment the thing you saw in your head runs in the world. The toll just collapsed. What’s on the other side is more of the part you loved.
Where I land #
If the keystrokes were only ever the toll, it’s tempting to let the hand skills rust. Keep your hands. Surgeons still open cadavers in an age of robotic assists; pilots still hand-fly approaches; the hand skill is still what everything rests on when the machine fails at 2 a.m. and someone has to descend through the abstraction and see. Your depth is the kernel the new craft runs on. What changes is the pricing: hand-speed stops being the product and becomes the qualification that makes your judgment worth multiplying. None of this comes with a schedule. The last mechanization included a fifty-year stretch economists call the Engels’ , where output per worker climbed while wages sat nearly flat; the gains were real, and they arrived a generation late. Expect a version of that, and don’t wait for the market to move you to the right side of the machine. It won’t. But move as a craftsman, not a convert. The tools are immature, the norms unwritten, and the standards of the new craft will be set by whoever shows up carrying standards from the old one. That is exactly who founded the profession in 1847. If the current agent workflow offends you, good. The Newcomen engine offended Watt (it threw away most of its steam), and instead of refusing it he rebuilt it. Refusing the tools forfeits a seat at that redesign. Bringing your taste to them is how you claim one.
A century from now someone will write the history of what happened to software engineering when the machines learned to code, and the shape is guessable, because we’ve run it before. Some engineers will tend the fleet at the fleet’s tempo, and some will edit its output at a tempo their judgment sets. Some will hand-write code for the few who pay for provenance. And some will walk toward the machine carrying their standards, and whatever they build there will get the next name. That last group founded my profession once already. I’d bet on them founding the next one.