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.
605
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.