I'm not a Luddite, and neither were the Luddites

Tools don't democratize outcomes. They just make the gap between intent and execution feel deceptively tiny.


“Vibe coding” is being sold as a magic shortcut, and I’m going to complain about it for a few hundred words. First, a disclosure: I got faster with these tools, so a person who benefits from them is telling you they won’t help everyone. Squint accordingly.

Typewriters didn’t turn everyone into novelists. Markdown didn’t either. (Typewriters did produce a staggering number of novels, most of them bad, which is closer to my point than I’d like.) LLMs trained on mountains of code won’t turn the general population into software engineers overnight.

Everyone can buy a hammer, but most people still hire contractors. Except people also watch one YouTube video and tile their own bathroom, and sometimes it turns out fine. I picked a shaky metaphor and I’m keeping it, because the hammer line is the part you’ll quote.

The trap is that generative AI makes the gap between intent and execution feel tiny. The model fills in the boilerplate, and it’s easy to mistake fluency for understanding. You get a prototype that looks like a product until you have to deploy it and keep it alive.

When a tool makes you ten times faster, the first fear is “if everyone has this, I lose my edge.” Express any caution about that and someone calls you a Luddite. The actual Luddites were skilled textile workers in early 1800s England, and their fight was over wages and who profited from the machines. So the insult is aimed at the wrong crowd, and given the fear I just described, it fits me better than I’d like.

Here’s my theory: frustration is the real architecture. The people who get the most out of a new tool are the ones who spent years on legacy bottlenecks and manual grunt work, and that frustration tells them what to build. I’ll admit that line sounds like a poster in a co-working space. Years of staring at a bottleneck give you opinions. They don’t guarantee taste. Some people stare at the crooked house for twenty years and never learn carpentry.

Then there’s the execution gap. Generating code and getting a system into production are different jobs. Production means failing, testing and chasing edge cases, and most people quit at the first friction, whatever tool they’re holding. I’d like to say I’m in the minority. I’d also like to be taller.

“Domain context is the moat” is what every LinkedIn consultant says right before pitching a course, so here it is without the moat. If you understand the constraints of a spatial analysis engine, a B2B marketplace or a constraint-solving math grid, the model’s wrong answers look wrong to you. That’s the whole benefit. It also cuts the other way: if you only think you understand the domain, the model will agree with you cheerfully.

Vibe coding will make people who understand their problem faster. It will also make people who don’t understand it confidently wrong at scale. You can hand off the boilerplate and still own the result.

If this makes you uneasy, good. Use that to learn the parts the model can fake but can’t solve.

Your edge is never the hammer. It’s knowing where to strike, because you’ve spent years staring at the crooked house. Or you’ve stared so long you’ve stopped noticing it’s crooked. Ask someone who just walked in.