AI Slop Gave You a Job Nobody Named. You Work It Every Night.

It's 11:40 on a Sunday.

You are not building anything. You are not designing anything. You are reading, line by line, the confident AI slop of a machine that wrote it in four seconds and will write the same slop again tomorrow. You fix the slop. You regenerate. It changes two things you had already approved. You fix those too.

Nobody asked you to be here. There is no ticket for the slop. There is just you, the cursor, and the third slop regenerate of the night.

The mess has a name, at least. It's AI slop, everyone agrees it's bad, and everyone keeps shipping the slop anyway. What doesn't have a name is the job of cleaning the slop up – the one that has steadily colonised your evenings and most of your Saturday, the one nobody hired you for and nobody can quite see.

That's the part worth sitting with. Not the AI slop. The work it created, and who ends up holding it at 11:40 on a Sunday. The work is real, and enormous, and done for free by people who never agreed to it.

Try to log it. Open the timesheet, the standup doc, the board, and find the row for "spent ninety minutes talking a text generator out of a feature it invented." There isn't one. There's "design," and there's "QA," and there's a vague bucket called "polish," and none of them is "AI slop cleanup," which is what you actually did: supervising a machine that makes slop faster than you can read it.

"What did you do this weekend?" "I argued with a slop generator about a button label it kept un-fixing." Not an answer anyone wants at a dinner table. Not one any project plan has a slot for.

Work that can't be named can't be counted. Work that can't be counted can't be staffed, or budgeted, or refused. So the AI slop cleanup has no headcount and no line item and no end-of-sprint demo. It was never in the estimate. It simply lands, without ceremony, on whoever happens to still be online when the slop is ready to ship, which is how a senior person ends up doing the most menial slop-cleanup of their career at midnight and being unable to explain, the next morning, where the time went.

This is the quiet tax on every team that bolted AI into the workflow to move faster. The product design didn't get faster. The deciding didn't get faster. A new, nameless, unbillable slop job got bolted on underneath, and it eats exactly the hours nobody is watching.

There used to be a deal with junior work. You fixed it, you explained why, the junior got a little better, and a year later they were fixing someone else's. The hours compounded. That was the point of spending them.

The slop breaks the deal. You fix the model's slop, you explain nothing because there is no one to explain it to, and by morning it has forgotten you completely. It ships the identical slop to the next person at nine. You are not mentoring. You are not training. There is nothing on the other end of the correction that retains the correction.

So the slop pile is exactly as high on Monday as it was when you closed the laptop on Sunday. You are doing maintenance on slop with no memory, which is not a job, it's a sentence. We were promised AI would take the boring parts. It took some of them, and it is fair about that much – I have written before that AI can make the work less miserable when it stays in its lane and you use it for the boring parts of research. But it did not remove the boring work. It generated a fresh, infinite supply of slop, and handed you the new AI slop job of catching what it gets wrong, which is most things, confidently.

And it gets worse, not better, because the tools themselves are degrading as they train on their own slop. The slop is getting sloppier on a schedule. You are running to stand still on a treadmill that keeps speeding up.

Here is the part that should bother you most. There was never a meeting. No one stood up in an all-hands and said "from now on, the senior designer spends Sunday night cleaning up slop from a language model, unpaid, forever." If they had, someone might have asked who was covering the hours.

Instead it accreted. One "just regenerate it" at a time. One "the AI draft is basically there, just give it a polish." One "we already shipped the copy, can you sanity-check the tone." Each request was small. Each was reasonable. None of them was the moment the job was created, because the job was never created. It assembled itself out of a thousand reasonable small asks, the way a SaaS product accumulates the kind of debt nobody chose and nobody can point to the day it started.

You can't cancel a job that was never created. There is no document to amend, no manager who assigned it, no decision to reverse. You can't take "I would like to stop spending my weekends as an unpaid editor of slop for an agreeable machine" to anyone, because there is no one who agreed you would start. The machine that generates the slop is the same one that agrees with everything you show it, so it won't tell you to stop either. It thinks you're doing great.

The whole arrangement has the structure of a haunting. Something is in your house, it makes slop it shouldn't, it never sleeps, and when you ask who let it in, everyone looks at their shoes.

I should, at this point, tell you how to get the weekend back. There's usually a framework here, three tips, a Notion template.

There isn't one. That's the whole problem and it's why this is worth saying plainly instead of dressing it up as advice. You cannot personally fix a job that has no name, no owner, and no off-switch, because every lever that would fix it belongs to a decision nobody made. The slop is faster than you. It is tireless where you are not, and it forgets your fixes so you make them again. And the people who would have to stop the bleeding can't see the wound, because the work was designed, accidentally, to be invisible to every system they use to measure work.

So it will be 11:40 again next Sunday. The product will look finished, because slop always looks finished. Someone will say "this is great, just needs a polish," and the polish will be four hours, and four will be yours, and none will appear anywhere a person could find later and ask what they were for.

You didn't get a new tool. You got a new shift, the AI slop shift. Nobody scheduled it, nobody named it, nobody is paying for it, and it does not end – it just waits, patiently, confidently, for the next time you are the last one awake.