Once upon a time, I was a 10x coder.
Seriously, I really was. I’ve written by hand something like 2 or 3 million lines of code in my life. A ridiculous amount. Speak 40-ish programming languages pretty comfortably. I wrote assembly in middle school. I’m a high-speed touch-typist, so I’ve never been limited by the speed of the keys. I used to count how much I’d built not by how many lines of code I’d written each day or week but by how many keyboards I’d successfully burned out that year. (At least up until I ponied up the money on a good mechanical keyboard, that is!) Coding is old enough hat that I said in job interviews, “As a general rule, if you need something built, I’ve already build twelve of it.”
I’ve had titles like Principal Developer, Principal Engineer, and Principal Architect going back more than a decade, and today I nominally wear the Manager hat, but realistically I still spend a lot of my time wearing some kind of software engineering hat.
Skill and talent and experience were pretty good moats while they lasted.
I still code these days, but in the last year, it’s become increasingly few and far between. Claude doesn’t code better than I do, but it definitely codes faster. I say what I want, and code that’s “good enough” comes popping out the side of the magic box in a couple minutes flat, for most problems. At regular intervals I still have to say, “No, you didn’t follow instructions, that’s not what I told you to do,” but even with that, in an hour I can now produce a day or two’s worth of work.
I don’t love the resulting code, to be sure. It’s kinda mediocre. Above average, maybe. B. Not B+, not B-, just a really solid B. But having worn the Principal hat for years and having had to review craptastic code from enthusiastic Mid-tier devs who couldn’t tell the difference between a mulberry bush and a red-black tree, I’ve honestly dealt with — and had to fix — far worse.
But the joy of code really is gone. Every codebase from now until the end of time is instantly a legacy codebase the moment it’s first created.
Imagine it’s the old days, and you’re a startlingly fast courier. You can run from hill to hill in the time it takes most people to walk across their lawn. You’re the go-to person for getting messages from hither to yon, and everybody knows that if it has to be done right, it comes to you, and you can readily and handily beat even someone who thinks they can beat you on horseback.
And then one day cars are invented. The joy in what you were doing was in the act of doing it, of being able to accomplish a feat most people couldn’t imagine pulling off, but now everybody can arrive quickly. People valued you for what you could do, and you valued it for what it felt like; but now? Well, nobody needs a runner when there’s an internal combustion engine. You’re still super-capable, but who cares?
The value you still have is that you still know better than most which way to go. You’re still pointed toward the right destination, driving your car, while a lot of others start off on the wrong road entirely. You still arrive first. You still took the most efficient route to get there.
Small consolation.
I mean, look, realistically, it’s still a lot better than trying to be a junior in this environment. If you’re a recent software engineering grad just trying to get your feet wet, your goose is 10,000% cooked. And I sympathize with your plight. Not if you were just joining the ranks of the coders because you saw the Big Bucks, to be sure; but if you got yourself a compsci degree because you, like I, were endlessly fascinated by what these amazing machines could do, I totally get it, and I’m sorry you had to Live in Interesting Times. Something of value has been lost.
I find myself now stuck on the same questions. What do you craft when no-one wants a craftsman anymore? What do you build when the act of building is no longer meaningful to anyone except you? Does it still matter to be a Master Carpenter when the world’s moved on to cheap plastic furniture and particle-board bookshelves? What do you tell those still coming up, those who look at your skill and experience with awe? What do you say, knowing that no future generation will ever again run the paths you ran, or feel the runner’s high as a particularly tricky algorithm comes to fruition after exhausting hours of deep concentration? What even is the path now to reach where you are from where they stand?
The business world never really liked having software engineers on staff: We were tolerated because we were needed. And, to be sure, people still need things to be built, and people need those things to be designed and built well enough that they don’t break. People still need Principal levels of experience and judgment, and AI still seems to be horrendously bad at both of those.
But consumers are more than happy to settle with plastic.
Lest there be any doubt, I didn’t use AI on this essay. These are my words, for better or for worse. AI would probably tell me to tone some part down, or stretch it out, or rework some part because it could offend someone. But you know what? Just because I can use AI for everything doesn’t mean I want to. The rough edges and odd metaphors and turns of phrase are all mine, and I’m going to claim each and every one of them — right down to this em-dash.
(Can’t even use em-dashes or an Oxford comma without AI overtones anymore either; but you can pry the two spaces after a period from my cold dead touch-typing hands.)