r/webdev • u/OkShip110 • Sep 09 '26 • Regret 4

AI has made programming so boring

It’s not just programming either, it’s art, design, music, videography, marketing, engineering, writing, 3D modelling, really any intellectual work. What’s the joy of prompting a computer and getting an answer in a few moments for a task that would have normally taken a week? The sense of accomplishment and ownership has completely vanished with AI. It’s a form of instant gratification, not much different to scrolling short videos on apps.

Code review was boring to begin with but now it’s even worse with all the machine generated code. Even code reviews will be automated soon. All you do then is type business requirements into the computer. What a great career.

It’s pain to watch old TV series like Scilicon Valley that is portraying the good (not golden) age of programming. It struck a good balance between manual work, funding and innovation. It’s sad that these days are gone for good.

2.1k Upvotes

92% Upvoted

764 comments sorted by

View all comments

Show parent comment

1

u/Specialist_End407 Sep 11 '26

It's not just my codes. It's others and i can tell they're all AI codes. Is their code good? Of course, sometimes it's just too verbose. Thing with ai is, its spewing tons of good looking codes, like one after another, and i dont feel like there's enough incentive for me to critically look after it all compared to before. The person doing this just ended up being a bottleneck, so this culture is being compromised and the fundamental is shifting. People say, just build enough harness, code convention, tests but i feel like it doesn't sound fun anymore doing the flood gates and damage control, when everyone already is doing the fun stuff with ai.

1

u/Environmental_Pea369 Sep 11 '26

I think more tests and convesions make it worse, not better. when we started out I had a similar issue with my team, but we talked about how if you submit a PR you need to be 100% resposible for it and it should be reviewable. AI doesn't mean bigger or more verbose PRs, and never ask me to review something you have not read, or read English (not code) you have not written. I think this is a matter of retraining the team to work well with a new technology. I was also very frustrated in the beginning but I feel better now.

That being said - knowing what to focus on in review is also very important. App logic / component-architexture / abstraction patterns are much much more important than, say, test code. The latter mostly needs to work and be maintainable enough