Somewhere between the third cold brew and the fourth refactor of a function nobody asked you to touch, a certain kind of developer decided they weren't an engineer anymore. They were an artisan. A craftsman. A maker of small, beautiful things, like a guy in a linen apron selling $14 sourdough at a farmers market.
The phrase floated through Hacker News this week — "Don't call yourself an artisanal programmer" — and the comments section lit up with 28 replies' worth of people either nodding furiously or defending their hand-thrown ceramic mugs. The fact that this even needs to be said tells you how deep the rot goes.
Here's the problem, and it's not just vocabulary.
"Artisan" Is a Compliance Code Word for "I Won't Ship"
Watch what happens in a code review when someone invokes craftsmanship. Suddenly the argument isn't about whether the feature works. It's about purity. The variable names must be poetic. The abstraction must be philosophically consistent. The commit message must read like a haiku written by someone who has never met a deadline.
Meanwhile the login button still doesn't work on Safari.
Artisanal programming is the aesthetic wing of scope creep. It's how a two-day ticket becomes a three-week monastic retreat. I've watched teams burn a sprint rewriting a perfectly functional module because the original author — a monster, clearly — used a for-loop instead of a recursive lambda that only three people on Earth can parse.
Nobody ever got fired for shipping something ugly that worked. Plenty of artisans get fired for shipping something gorgeous that didn't.
There's a reason the craft movement thrives in companies with too much runway and too little accountability. When you're pre-revenue and the CEO is on a podcast, nobody's measuring whether the thing loads. Aesthetics become the only scoreboard that matters.
Real Craft Has Customers. You Have Stakeholders.
Let's be honest about what an actual artisan does. A woodworker sells a table to a person who will put plates on it. A potter makes a bowl that holds soup. If the table wobbles, the customer comes back angry. If the bowl leaks, the potter eats the cost.
The artisanal programmer has no such feedback loop. The "user" is abstract. The "product" is a repository. The only person who truly evaluates the work is the author, gazing into the diff like Narcissus at the pond.
This is why so much "crafted" software is hostile to use. It was designed for the pleasure of the builder, not the relief of the user. Every gorgeous animation that makes the app feel like it's wading through molasses is a small monument to the developer's taste and a middle finger to the person trying to pay a bill.
The best engineers I've known — the ones who've lasted 20 years without burning out or getting managed out — share one trait. They're mildly embarrassed by their own code. They know it's a pile of compromises held together by tests and hope. They ship it anyway, because the alternative is shipping nothing.
The Cult of the Solo Genius Is a Recruiting Lie
There's a darker edge here. Artisanal framing quietly devalues collaboration. If code is a personal expression, then code review is criticism of you. If architecture is your signature, then a teammate's refactor is vandalism.
I've seen PRs sit for days because the author couldn't stomach someone "simplifying" their elegant solution. I've seen engineers quit over a merged branch. That's not craftsmanship. That's ego with a Git history.
And the companies love it. An artisan who identifies personally with the codebase is an artisan who won't demand a raise, won't push back on crunch, and won't leave — because leaving would mean abandoning their life's work. It's the same trick restaurants pull with "passionate" chefs who work 80-hour weeks for tips.
Call it craft, and you can call it exploitation without anyone noticing.
What We Actually Do Is Closer to Plumbing Than Pottery
Here's the unglamorous truth: most of this job is maintenance. Moving data from one shape to another. Fixing leaks. Replacing a corroded joint before the whole building floods. It's essential, it's skilled, and it's profoundly unsexy.
Plumbers don't call themselves artisans. They call themselves plumbers, they charge $180 an hour, and they go home at five. They don't spend weekends agonizing over whether the pipe expresses anything.
I'm not saying build garbage. I'm saying the pursuit of beauty is a tool, not an identity. Reach for elegance when it buys you something — readability, performance, fewer bugs. Stop reaching for it when it buys you nothing but a warm feeling and a delayed launch.
The developers who ship the most useful things tend to have a ruthless streak. They kill their darlings. They delete the clever abstraction. They write the boring code and move on, because the next problem is already at the door.
The Word Is Doing Damage at the Hiring Table
And it's not just internal. Put "artisanal" on a job listing and watch who applies. You'll get people who want to spend six weeks on the design system and zero weeks on the error states. You'll get portfolios full of side projects that are gorgeous and abandoned.
You'll also scare off the people you actually need — the ones who've maintained a legacy system for a decade, who can triage a production fire at 2 a.m., who understand that shipping is a moral act because someone is waiting on the other end.
The word isn't neutral. It's a filter, and it's filtering for the wrong humans.
So here's the ask. Next time you feel the urge to describe yourself as an artisanal programmer, close the tab. You're not a cheesemaker. You're not a blacksmith. You're a person who moves logic around for money, and the sooner you make peace with that, the happier you'll be.
The code doesn't care what you call it. Neither do your users. And honestly? Neither should you.
