Paid to delete AI code: is cleanup a real business or Sisyphus's labor?

The pitch is blunt. A client calls asking for a "small refactor" and hands over 100,000 lines of AI-generated spaghetti. To Slopfix, that isn't a headache. That's the whole business.

In brief

Slopfix is a three-person software house with one product: deleting AI-generated code. One week, three senior engineers, $10,000, and the bill scales to results. Promise a 50% cut, hit 20%, and you pay $4,000, with a two-week warranty on anything they break.

The thread split fast. Some engineers say cleaning up after coding agents is already their best-paying work; others call it Sisyphus's labor and would rewrite from scratch. And the anti-slop pitch itself reads AI-written: the shop admits it uses Claude Code to do the deleting.

A software house that bills for subtraction

Maciej, one of the three Slopfix engineers
Maciej, one of the three Slopfix engineers

Slopfix sells one service: deleting AI-generated code. Its pitch names a job that barely existed a year ago. A client asks for a "small refactor" and hands over a codebase that grew until, in their words, "the agent stops seeing the whole picture and starts duplicating code instead of finding it."

The method is deliberately un-magical. They analyze the codebase for free; if they can't help, you pay nothing. Before touching anything, they write down what the app does "screen by screen, endpoint by endpoint," and that checklist is the safety net. You get the refactored code, QA notes, and guardrails: a CLAUDE.md, lint rules, CI checks. Reduction is measured with scc on non-blank, non-comment lines, and "code golf" is banned so nobody games the target by crushing readable code into gibberish. They use Claude Code themselves, but, as they put it, "the agent doesn't get a vote."

"Removing the first 30% is easy"

The founder showed up in the thread to explain where the money actually is. Cutting the obvious dead weight is trivial; the price is meant to sit on the part that isn't.

"Removing the first 30% is easy. The next 30% is harder, and that is exactly what the price should be on: doing what others can't." — the founder of Slopfix

Not everyone believed the hard part is worth attempting at all.

"The real solution would be to hire old-style developers to rewrite the whole slop from scratch… Fixing broken slop is Sisyphus's labor." — a C/C++ and Unix engineer

Teams that ship slop on purpose, and stay happy

Others in the thread already live on the paying side of this problem, and they aren't complaining.

"We have been doing this for years now: it is great. We build our products faster and better and we get more money for fixing products vibecoded by others." — an engineer who built a business fixing others' vibecoded apps

The demand exists because plenty of teams pick the slop knowingly. One described retiring a $120,000-a-year low-code platform entirely by "vibe coding," with a revealing note about how they review it:

"We have senior engineers review the actual functionality and none of them have read any more than a few lines of code." — an engineer whose team replaced a $120k/year platform this way

The irony no one could unsee, and the cheaper fix

To several readers the marketing copy for an anti-slop service reads exactly like AI wrote it, and the shop confirms it uses Claude Code to do the deleting. Simon Willison went after the root cause instead:

"Sounds like you forgot to have the agents use red/green TDD and build a robust test suite while they were shipping all of those features." — Simon Willison, creator of Datasette

The sharpest jab was structural. If the first step is writing a full spec of what the app does, and that takes only a sliver of a week, then:

"…perhaps neither AI nor consultants were required." — one engineer doing the math on the one-week plan

That is the quiet verdict under the jokes. The thing that makes cleanup possible, actually knowing what your software does, is exactly what the slop skipped in the first place.

Get breakdowns like this every day

The top Hacker News stories, unpacked — by email, Telegram, or RSS.

Next story · 10 of 29 Read more
🌍Other

The mapping app that hides OpenStreetMap's schema until the moment you need it

Walk past a mailbox and StreetComplete pops one question: what are its collection times? Answer it, and the edit lands in OpenStreetMap under your name — no tags, no wiki, no idea you just touched a database.

★ 710 · 💬 171 · streetcomplete.app · 3 min