Your Job Was Never Writing Code (You Just Didn't Notice)

The discourse is spiralling again. 'AI is replacing developers!' screams one camp. 'Real engineers still hand-craft every line!' shouts the other. Both are missing the point so badly it's almost impressive. Here's the thing: writing code was never actually your job. Solving problems was. The code was just the annoying middle bit. Think about it. When was the last time a product manager came to you and said 'please write exactly 347 lines of TypeScript'? Never. They came with a problem. Users can't check out. The dashboard loads like it's 2003. The API falls over when more than three people breathe on it. You solved those problems. Sometimes with code. Sometimes with a config change. Sometimes by realising the problem didn't need solving at all. The code was just your interface to the solution, like a painter's brush or a chef's knife. Now we have better interfaces. Cursor writes boilerplate. Claude refactors legacy nightmares. GPT-4 generates that schema migration you've been putting off. And suddenly everyone's having an identity crisis because the part we pretended to hate (writing yet another CRUD endpoint) got easier. The valuable skill was never syntax memorisation. It was knowing which problems to solve, how to architect solutions that don't explode in six months, and understanding the trade-offs between shipping fast and shipping right. AI can't do that. It can barely decide between a Map and an Object without hallucinating a third option. What's actually happening is the job is returning to what it always should have been: thinking deeply about systems, understanding user needs, making architectural decisions, and yes, reviewing and directing the code that gets written, whether by you or an AI. If your entire value proposition was memorising React hooks or writing for loops, then yeah, you might be cooked. But if you were ever actually good at this job, you were already doing the part AI can't replace. The developers freaking out about AI are the same ones who freaked out about Stack Overflow, or jQuery, or high-level languages in general. Every abstraction layer triggers the same panic. Every time, the people who adapted thrived. So no, your job isn't writing code anymore. It never really was. And that's completely fine. The sooner you accept that, the sooner you can get back to the actual work: building things that don't suck.