I liked programming a lot, but with AI and how my company is basically requiring us to use it for AI-first development I’m not enjoying my job anymore…
It feels like forced effort on my part to write design documentation and refine it so the LLM does it the way I want and having to review the prompt continuously opposed to actually solving problems the way I would. Plus things aren’t even supposed to be reviewed until an AI review of the AI code is done… I just feel like I’m supposed to be a rubber stamp on the output. They say that dev/review skills won’t atrophy because you’re always reviewing the code, but I can’t accept that conclusion. I became a better developer by actually problem solving, not reading code to see if it makes sense. It’s all about getting more done and trusting it at a conceptual level now, but not really understanding what’s really going on underneath the AI-gen docs because it’s “so much better than human-generated code”.
I don’t understand or really handle that approach well. I don’t really program outside of work because I want to just hang out with my family after it and it feels like a chore to do my job anymore. I just don’t know how to make myself enjoy that type of workflow they are trying to force onto everyone. Any ideas on how to find something to enjoy with that?


when the US outsourced manufacturing, its domestic technical skill base (machinists, welders, etc) atrophied. Today, some are attempting to redevelop these skills and it may take a decade minimum.
Its a cautionary tale. I would say try to hang on until the AI bubble bursts and then advocate for keeping a healthy domestic skillbase
A lot of those skills won’t come back or they’ll be more specialized.
My friend works in auto manufacturing. He welds truck frames. Except he doesn’t weld by hand at all, he uses robots to do all the welding. He can supervise a whole team of robots and adjust them to deal with flaws as well as set them up for new jobs. As one person he replaces a whole team of welders.
Now don’t get me wrong, there still are lots of manual welding jobs out there, but a lot of them are specialized into custom work or in complicated scenarios (underwater dive welding on oil rigs). The standard manufacturing line job where you perform the same welds over and over again is a thing of the past.
Welding a frame is a repetitive task, and the robots are deterministic. Programing is not repetitive, every problem is different and takes creativity, and LLMs are not deterministic.
I used to say that for a long time. But I am starting to doubt it’s gonna burst. I mean the valuations are probably way too high, but we’re never going to put the cat back in the bag. Programming is changed forever with AI. I’ve been a programmer for 25 years professionally and I am working on integrating AI in my daily work routine. I see it this way: We’ve had tools for decades that helped us write code. When ReSharper was introduced many years ago it was able to speed up writing code for all .NET programmers by suggesting snippets of code or performing large refactoring for you. Obviously AI is a whole other level, but it’s still just a tool.
I was never particularly proud of how much Stack Overflow I had memorized anyway. That wasn’t the fun part of my job.
Most of these companies pushing AI so they can show half their devs the door are insane. You can’t just vibe code shit and expect results other than a full airline ground stop and Microslop Office being down worldwide.
The AI is pretty worthless without me. I have zero concerns about being replaced by a project manager. Companies are being sold something else, but they’re gonna figure it out pretty quickly. (Though not quickly enough for some of us. Negotiate to keep your tenure and severance when they bring you back .)
But AI as a tool is here to stay, and it’s better to build those skills earlier than later. The Riemann hypothesis shows a bit of a model for future work, both good and bad. You can’t just tell AI “solve the Riemann hypothesis”. It would have gotten nowhere without the expert guiding it and using it as a tool. Fortunately most of the stuff we’re doing isn’t cutting edge research, so hopefully we don’t have to deal with a pile of slop that we can prove is correct, but nobody understands how.
Out of interest, how do you recommend someone learn to use it as a tool and not over rely on it?
A couple ideas here:
Yesterday I was using Copilot and Claude to write a clone of the old
trnUsenet newsreader in Rust. Got pretty far in about 7 hours. 8300 lines of code and 8300 words of design docs in Markdown. The architecture is pretty good, and the thing works. (Still missing is the thread graph display and posting, but I know those can be added without breaking anything.)Don’t get me wrong: if there were a button that destroyed LLMs forever, I’d have already pressed it. I have other projects that I write by hand even though LLMs could definitely do it because I like the challenge and I want to stay sharp. Reading code doesn’t do it.
Yeah, I don’t have a good answer for that. I’ve seen how easy it is to get lazy and just vibe with whatever it’s putting out, in others and myself (sometimes).
The worst is when it’s clearly not working and the person just spins the AI in circles with “well, fix it” over and over again.
I do think we have a history of looking for black and white answers that has bitten us in the ass. “Not invented here syndrome” led to the npm dependency hell, for example. There’s a middle ground. log4net and whatnot are great third party tools that should absolutely not be reinvented yourself. But maybe you should have handled Leftpad on your own.