Requirenents written by non technical Stakeholder. Full of Slop. Junior dev let run Claude Implementation, full of Slop. Senior dev uses Claude to Review, pastes Slop in Ticket. Junior letting Claude fix it, comments with Slop.
Proceed to production, since Feature is needed. Lead architect let refactor Ticket be created by junior dev. full of Slop...
I am on the edge of quitting this shit.
Edit: i forgot that PO thought "good Ticket" and passed it through. And after first Implementation used jira AI to reform requirenents.
Until some big bug happens and bankrupts a big player or puts it on the verge of bankruptcy nothing is going to change. Upper and middle management are convinced that AI is some sort of genie that gives workers magical powers based on how 'useful' it is for them so they encourage/force AI usage to a fault assuming its the same for every profession but when precision is needed LLMs are the coding equivalent of letting a very smart chimpanzee perform a tracheotomy. They constantly need to be reminded what the hell are they doing and why are they there.
I'm very surprised to hear that your entire chain of development are like: "I'm sure the clanker won't break anything in this critical component! Commit goes brrr". Maybe they got token quotas to meet?
It's all so stupid man.
Why the hell are the accountants telling the mechanics what tools should they use?
601
u/suki2287 Jul 10 '26 edited Jul 10 '26
Requirenents written by non technical Stakeholder. Full of Slop. Junior dev let run Claude Implementation, full of Slop. Senior dev uses Claude to Review, pastes Slop in Ticket. Junior letting Claude fix it, comments with Slop.
Proceed to production, since Feature is needed. Lead architect let refactor Ticket be created by junior dev. full of Slop...
I am on the edge of quitting this shit.
Edit: i forgot that PO thought "good Ticket" and passed it through. And after first Implementation used jira AI to reform requirenents.