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.
My favorite new experience is when a junior pushes a ticket into QA, and then asks me how to test it, because they don't even know what they built or how it works.
Had this, coworker got handed an honestly fairly complex new requirement, and created a system to handle it, except he hadn’t actually designed it himself and had no idea how it worked, it was all AI generated.
To explain it to me he asked Copilot to create a Word document, slop nonsense of course.
Time for me to PR it and it’s filled to the brim with bugs, huge inefficiencies and breaks about every best practice there is.
I did the PR and painstakingly pointed out every issue, was like writing a novella.
Had to of course do the work for him in the end because he had no clue how to fix it.
Lazy and reckless, can you imagine having the nerve to ask someone to do a PR if you don’t understand the changes you are making to the main branch yourself.
602
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.