Go back and re-read the quote from your comment - which I responded to: “ You will not convince the person drowning you in 2000 line PRs to stop. Start looking for a new job as if you have already been fired.”
I’m not overreacting to some nuanced take here. I’m not sure how to characterise quitting as a response to over-enthusiasm / slop as anything other than the career equivalent of sticking your fingers in your ears. I’ve been there, I’ve had the arguments, I have little sympathy for staff/principal engineers or above who react like this - their job is to fix the organisation, put a yoke around the beast of AI and find a way to tap the benefits and use the problems (like those 2000 line PRs) as a golden signal for where you need to educate and improve process and planning.
Again - I’m not selling anything here, I just have found it an interesting challenge over the last year and one where I’ve been happy to make progress organisationally despite the frustrating moments. If someone’s response to a problem like this is to throw their hands up in despair or to engage in whatever the logical opposite of AI-hype is (which the article resorts to repeatedly) then yes I’d worry about being laid off. If you’re in an organisation where you don’t have the agency to fix problems then absolutely - start looking for a new job.
[0] https://pluralistic.net/2025/12/05/pop-that-bubble/#u-washin...
[1] https://pluralistic.net/2026/01/05/fisher-price-steering-whe...
This exact situation occurred to me. I blocked all PRs with “request changes”. Most engineers don’t like AI slop, most take pride in their work.
The occasional AI slop engineer can be contained by rejecting their PRs, having team discussions around norms, bringing up feedback on retros, etc.
> Most engineers don’t like AI slop, most take pride in their work.
Do you work in an industry that requires good code? Perhaps you are just really talented and gotten hired by companies who demand excellence OR you're just really lucky. I'm a pretty run-of-the-mill developer (I care a lot about my craft but I'm not a "10xer" or whatever) and in my 20 years at, uhm, 5 or 6 different companies (once which was FULL of people who gave a shit), I would not say that "most" engineers don't take pride in their work, not even close. Most just want to finish up and get home.
> If you’re being asked to review huge volumes of terrible AI code, just assume that the organisation is going to burn you out and fire you. You will not convince the person drowning you in 2000 line PRs to stop. Start looking for a new job as if you have already been fired. I have seen this happen many times now
I suspect we will see this phenomenon more and more as organizations more widely adopt agentic development.