The essay opens with a farrier in Mandres-en-Barrois, a small village in rural France, watching the automobile arrive and deciding to become a mechanic. Four generations later, his great-great-grandson — a software developer — watches AI roll in and recognizes the same dread. The structural move is clean: displacement anxiety is not new, but what persists across it might be the thing worth holding onto. The core argument is that purpose outlasts tooling. The family didn't stay in the horse business; they stayed in the moving-people-around business. The author extends this to developers: if what you actually love is making things, solving problems, and watching people use what you built, then the specific act of writing code is the horse, not the destination. "Be willing to let go of the how to hold on to the why" is the essay's thesis, delivered in its final line. This is a personal essay, not a labor economics paper, and the author is honest about the limits of his evidence. "Not every farrier became a mechanic, and I'd never have heard of the ones who didn't. So I won't pretend his story proves anything." That's a good sentence. It disarms the survivorship-bias objection before the reader can raise it, which earns the essay room to make its emotional argument without pretending it's making an empirical one. What the essay does well is reframe the AI anxiety conversation away from capability forecasting and toward identity. Most developer-displacement discourse is about whether LLMs can write production code (they increasingly can) or whether they'll plateau (unclear). This piece sidesteps that entirely. It doesn't matter whether AI replaces 30% or 90% of coding tasks; the question is whether you defined yourself by the task or the purpose behind it. The limitation is that the analogy, while emotionally resonant, elides real structural differences. A farrier could retrain as a mechanic in the same village with the same customers. The transitions AI threatens may not be so geographically or economically smooth. The essay doesn't owe you a policy paper, but the gap between "my great-great-grandfather pivoted" and "therefore you'll be fine" is larger than the narrative implies. Still, as a piece of writing aimed at anxious developers doomscrolling at 7am, this does exactly what it needs to do: it slows you down, gives you a longer timeline than your Twitter feed does, and asks you to locate what you actually care about underneath the tools you currently use. That's a useful intervention, even if it's not a complete one.
