Coding as Craft: Going Back to the Old Gym

I also appreciate the craft of coding. My suspicion is that eventually it just won't be a thing anymore, even though such a future is not my preference. Not that humans will be completely removed from coding, but writing every line yourself will just be incredibly uncommon and not industry standard. I'm not good at predicting, this is just where my gut is right now.

Very good article. I try to (respectfully) push my coworkers in this direction but it’s a bit of a lost cause.<p>I work mostly on small codebases and you can smell unchecked AI codegen from a mile away. Even small changes become giant refactors.<p>People who push this have never had to work in such codebases. God forbid your requirements change mid project. Rarely does the sum of separate prompts without full context result in something maintainable and modifiable. You’re cooked.

For me it’s not complicated when to use AI. If the task is something where having fluency will make me significantly more productive and nimble in the future, then I’ll go the old gym way.<p>It’s like communicating in a foreign language- you can do it with AI, but if it’s an essential element of your job then you’re going to invest the time to learn it so it becomes part of you.

This article really hit home—especially this part from the conclusion:<p>&gt; In a world pushing for “reflexive AI usage,” I’m advocating for something different: thoughtful, intentional collaboration with AI that preserves the essence of coding as a craft. &gt; ... &gt; Like Rocky, we sometimes need to step away from the comfortable, civilized environment and return to the old gym – the place where real growth happens through struggle, persistence, and focused practice.<p>&gt; Because coding isn’t just about output. It’s about the journey of becoming better problem solvers, better thinkers, and better engineers. And some journeys can’t be outsourced, even to the most advanced AI.<p>But here’s the reality: those ideals feel increasingly out of reach. Business demands and short-term thinking rarely leave room for “intentional” or “thoughtful” work. For many of us, having time to grow as engineers is a luxury.<p>Worse, it’s often personal. I’ve had to carry the weight for friends in crisis, pretending two people were working just to help someone keep their job. It’s brutal—and sadly, not rare.<p>As AI gets more buzz, many stakeholders now think our work is overvalued. A quick AI PoC becomes “good enough” in their eyes, and we’re expected to polish it into something real—fast, cheap, and under pressure. Meanwhile, we’re constantly defending our craft against the next threat of being replaced by “cheaper” labor.<p>When I started out, we cared about clean code and craftsmanship. Now, I feel like I should be taking sales courses just to survive.<p>Today, it’s all about output. Ship faster or get replaced. Quality only matters when it’s too late—after the person who made the bad call has already cashed out.<p>I know this sounds pessimistic, but for many of us who aren’t in the top 1% of this industry, it’s just reality.<p>Thanks for the article, Christian. You’re not wrong—but I think you’re one of the few lucky enough to live that perspective. I wish you all the best, and hope you can keep enjoying that rare luxury. There will be a need for true craftsmen—especially when the rest of us have gone numb just trying to keep up.

I think this fails to recognize how many more important problems there are in the world, and that the writing of code was not meant to be one of them, but only came into existence to <i>solve</i> them.<p>Of course, that does not have to be true now. You can certainly do this for personal satisfaction.<p>But the argument in this article is a bit confused. The step that lies behind &quot;coding&quot; is not of lesser difficulty, on the contrary. Instead of worrying about coding, we can instead worry about the bigger picture, and all the beautiful thinking, contemplating and deadlock it entails.<p>Only now, we are one step closer to solving a real problem.

This reminds me that I should do more coding challenges. Maybe nothing major, small data wrangling. Stuff like puzzles in the game Human Resource Machine. Advent of code light maybe. So refreshing and fun sometimes.

My anxiety for where this is all going is as follows. Using AI for all your coding is a wet dream for CEOs because the goal is to fire all their engineering staff except for a handful of maintainers. However, it reminds me of trying to explain to your stakeholders why you need time to work on tech debt before it becomes a problem. There is no metric now that says there is a problem that’s easily measured but engineers are grinding their teeth trying to work within a system that is slowly degrading and is showing signs.<p>“Who cares, ship it, also we need this new feature next week. What do you mean it will take longer this time? Ridiculous, why didn’t you say something before?”<p>Likewise, the brainrot and lost knowledge, as well as possible new tech debt that fewer engineers working in their codebase understand, will eventually cause issues down the line. The same pressures will ensue causing stakeholders to ignore all the signs of degradation.

&quot;Generating boilerplate code, Summarizing documentation, Understanding complex concepts, Debugging tricky error messages, Drafting unit tests, Formatting data&quot;<p>Thing is, this is probably 99% of the programming work of a junior dev at a place where management thinks like that.

&gt; The phrase “reflexive AI usage” is what triggered my strongest reaction. “Reflexive” suggests unthinking, automatic reliance. It implies delegating not just tasks but judgment itself.<p>Does it? When I trained as a schoolteacher, we were required to engage in &#x27;reflexive practice&#x27;, meaning at the end of the school day, we were expected to sit down and think about - <i>reflect</i> - on what had happened that day. I don&#x27;t know how the Shopify CEO meant that phrase, but &#x27;reflexive AI usage&#x27; has two conflicting meanings - it can be AI usage that is either actively or passively chosen - and we might need some better phrasing around this.

&gt; If people stop the occasional deadlock of grinding teeth, looking at a problem, crying, going for a walk, praying and screaming until suddenly it makes sense (and you learn something!), I’d call it severe regression, not progress.<p>People for which development is not their job will absolutely want to get rid of it as much as possible because it costs money. I really agree with the author, it does feel like a regression and it’s so easy to overlook what makes the most part of the job when it looks like it can be fully automated. Once you don’t have people who are used to do what’s quoted, and there is 500 million lines of code and bugs, good luck with that to ask a human to take a look. Maybe AI will be powerful enough to help debugging but it’s a dangerous endeavor to build critical business around that. If for any reason (political or else) AI got more expensive it could kill businesses (twitter api ?)

Really interesting and I agree with everything. With my team we always try to improve our programming skills without AI, even though we all recognize its great utility.<p>Today every type of problem and every type of solution seems to have to be solved with AI, when there are more creative, original and artisanal ways to solve them (even if, sometimes, they need more time and patience)

Yeah, anytime I am about to do some long multiplication, I start reaching for my calculator and stop, &quot;no, you will go to the multiplication gym, and do this by hand, need to stay sharp&quot;

&gt;&gt;It won’t design your domain layer with the care and consideration that &gt;&gt;comes from deep experience and hard-won knowledge.<p>What if every time you had an Aha! moment, you blogged about it in detail. Many people do. AI ingests those blog posts. It uses what they say when writing new code, or assessing existing code. It does use hard-won knowledge; it just wasn&#x27;t hard-won by AI itself.

&quot;It’s about maintaining the human element in a craft that’s increasingly automated.&quot;<p>I mean, what can anyone do, anyway? We’ve been on a &quot;quest&quot; toward the total automation of work for decades! and unfortunately these reflections are coming far too late.<p>didn’t anyone notice what was happening all these years?<p>Talking with a musician friend, he pointed out that today, studying, producing, and releasing music is almost volunteer work because the vast majority of artists will likely see no return on their investment, especially with AI flooding the music platforms, so I really expect it to happen to many other jobs.

I like the article.<p>At the same time, as AI takes over the actual coding practice more and more, I find the situation with multiple programming languages a waste of resources.<p>If AI could generate binaries, web assembly directly, or even some &quot;AI specific bytecode&quot; then we could skip the steps in the middle and save a ton of energy.

Even delegating just the boring parts doesn&#x27;t appeal to me.<p>Generating boilerplate code - getting frustrated about code is what drives new ideas and improvements, I don&#x27;t want to lose that friction.<p>Summarizing documentation - Reading and making sense of written material is a skill.<p>Explaining complex concepts - I don&#x27;t want explanations on a silver plate, I want to figure things out. Who knows what great ideas I&#x27;ll run into on the way there.<p>Helping debug tricky error messages - Again, a skill I like to keep sharp.<p>Drafting unit tests - No one knows better than me what needs testing in my code, this sounds like the kind of unit tests no one wants to maintain.<p>Formatting data - Maybe, or maybe whip out Perl and refresh that skill instead.<p>Keep delegating everything to AI for a year and I suspect you&#x27;ll be completely worthless as a developer without it...

But then again most IT jobs are the equivalent of flipping burgers at mcdonald&#x27;s, nobody&#x27;s asking them to be Michelin starred chefs.