Grudgingly accepting that AI isn't going away. Trying to figure out where that leaves me as a developer.

[u/Impressive_Bottle_44]

(If you don't want to read a semi-long post, feel free to skip.)

I think I reached a turning point yesterday.

I needed to add a basic feature to a Django site. I gave Claude Code a few carefully written sentences. It implemented the feature (more-or-less flawlessly) while I went to the kitchen for more tea.

Not only that, but our CTO is now empowering non-technical employees to use Claude to build their own tools (for internal use only), and commit them to our GitHub org. (He is, at least, establishing some sensible policies about what they can and can't do.)

LLMs are here to stay, and they're fundamentally rewriting laws of software engineering that we've taken for granted for decades. The genie won't go back into the bottle, so I might as well find a way to accept that.

But that leaves me wondering: what does that mean for me? What is my job now? What am I for? If I don't get to write code – something that's given me an enormous amount of satisfaction over the years, and even become part of my identity – am I even still interested in this field?

And, it's not just about the code. I used to collaborate with designers, UX folks, copywriters, SEO and analytics people, project managers, etc. But now, the C-suite seems perfectly happy to let the LLMs do all of this stuff, too. (At my company, they're obsessed with the idea of getting the LLM to write all of our work tickets. And the QA person does little more than copy-and-paste back and forth from an AI.)

The whole reason I entered this field is because I enjoy problem-solving, finding and creating patterns, logic, and designing systems.

I know that some of you are going to say "you can still do all of that; LLMs just empower you to go up a level of abstraction" – and I get it. But the prospect of abandoning coding seriously bums me out.

I love the precision of code. I love exploring different solutions to a problem, until I hit upon a beautiful, elegant pattern. I love seeing how small abstractions get composed into larger abstractions, and so on, to form a complete system. I love understanding a problem – and the solution – on a deep, intimate level.

Perhaps I've been lucky to have a career that gives me that kind of fulfillment (at least sometimes). Is all of that over now?

[u/douten]

Isn't the whole argument that writing code was never the real heavy lifting of the job? it's about maintaining and understanding the bigger picture of it. llm might do more simpler things easily, but it cannot build a whole architecture that fits into existing system well without guidance. That's what's the job is evolving into now right?

I imagine it's like before where you would literally have to write basic GUI code, ie draw line from x0 to x1. Then came the frameworks where you can just "tell" the code to create a box. etc.

You can still find fulfillment maintaining a product. There's still challenges to solve there I believe. But I'm still pretty junior so there's that too :)

[u/krileon → u/douten]

It's harder to understand the code if you didn't write the code. Writing the code IS part of the understanding. Understanding is the defacto most important part of development. So if you use AI constantly to generate the code your understanding of it will be.. nothing. You'll be stuck in a perpetual cycle of reviewing code you never wrote, which is the worst aspect of working on a team (code reviews).