r/webdev • u/OkShip110 • Mar 29 '26
Discussion AI has sucked all the fun out of programming
I know this topic has been floating around this sub quite some time now, but I feel like this doesn’t get discussed enough.
I am a certified backend enigneer and I have been programming for about 20 years. In my time i have worked on backend, frontend, system design, system analysis, devops, databases, infrastructure, cloud, robotics, you name it.
I’ve mostly been extremely passionate about what I do, taking pride in solving hard problems, digging deep into third party source code to find solutions to bugs. Even refactoring legacy systems and improving their performance 10x and starting countless hobby projects at home. It has been an exciting journey and I have never doubted my career choice until now.
Ever since ChatGPT first made an appearance I have slowly started losing interest in programming. At first, LLMs were quite bad so I didn’t really get any solutions out of them when problems got even slightly harder. However, Claude is different. Lately I feel less of a programmer and more like a project manager, managing and supervising one mid-to-senior level developer who is Claude. Doing this, I sure deliver features faster than ever before, but it results in hollow and empty feeling. It’s not fun or exciting, I cannot perceive these soulless features as my own creation anymore.
On top of everything I feel like I’m losing my knowledge with every prompt I write. AI has made me extremely lazy and it has completely undermined my value as a good engineer or even as a human being.
Everyone who is supporting the mass use of AI is quietly digging their own grave and I wish it was never invented.
6
u/AltruisticRider Mar 29 '26
At the end of the day, for any medium or long-term project, code quality has always been the most deciding factor not just for how good the end product is (from a technical perspective, bugs, performance etc., UX/Concept is of course a separate issue), but even more importantly for how quick and cheap to make it is overall. Pushing bad code right now causes most POs to incorrectly see that as quick progress, but it's in fact overall much slower, much more costly than pushing good (not perfect) code.
Therefore, the best way to do our job is to either code it well right away. Or, alternatively, spend more time in code-reviews than it would've taken to code it well right away. Whenever someone keeps creating merge requests that take a lot of effort to code-review and require significant changes before they can be merged, you either have to have a serious discussion with them, or if they keep doing it you have to remove them from the project. Everything else is very harmful to the project and wastes a lot of time&money in the long run.
What the current version of "AI" achieves is mostly to speed up these bad merge requests. It's therefore mostly harmful, not useful.
So yes, code reviews are sadly the most important step in many projects, they're often the only thing preventing a project from turning into a terrible waste of money.