Skip to main content Skip to footer

Got Slop?

Your AI built it fast. Now it's slow, broken, and unmaintainable. We're the cleanup crew for the vibe coding era. Sustainability for your codebase.

Get Pickup Service

Trusted by developers who've seen things. No annual contract required.

Always working for a sustainable codebase.™

Find Slop Management Services

We'll scan your repo and recommend a cleanup plan. Free for personal projects.

Slop Pickup & Recycling Services

Residential Slop Pickup

SM's curbside slop and code recycling pickup is the best choice for your repo, and for the ecosystem.

Get Residential Slop Service

Commercial Slop Pickup

SM's commercial slop and code recycling pickup is the best choice for your organization, and for the ecosystem.

Get Commercial Slop Service

Roll-Off Dumpster Rental

From weekend hackathons to Series B rewrites, SM has a dumpster that's perfect for your project.

Rent a Roll-Off Dumpster

NEW: Gitster® — Dumpster in a Repo. Buy today, fill it up, we'll come get it. Clone. Fill. Gone.®

Gitster® — Dumpster in a Repo®

Clear slop and debris with the convenience of a Gitster® repo. The flexible option for big cleanups.

Step 1

Clone

Gitster® repos are available on GitHub and npm. Clone one into your project directory and start filling it with slop.

Step 2

Fill

Small, but mighty. Gitster® repos are compact when initialized but can hold up to 3,300 files of debris, dead code, and abandoned features.

Step 3

Gone.®

When your Gitster® repo is full, disposal is quick and easy. Simply run sm pickup or schedule a collection online and we'll haul it away.

Capacity: 3,300 files  |  Weight limit: 50MB  |  Dimensions: 1 repo × unlimited branches × infinite regret

Find the Right Container for Your Project

From side projects to enterprise monoliths, SM has a container that fits. Pricing and options vary by tech stack.

Residential Containers (for recurring pickup)

32-File Container

Best for: Hobby code and failed startup MVPs

Up to 32 files of slop per pickup

For developers who code alone so nobody finds out.

POPULAR

64-File Container

Best for: Apps that have actual users (unfortunately)

Up to 64 files of slop per pickup

When your MVP starts becoming a problem.

96-File Container

Best for: Production apps with accumulated sins

Up to 96 files of slop per pickup

Our most popular residential container, ideal for teams who argue about code style.

Roll-Off Dumpsters (for project cleanups)

10 kLoC

4 repo loads

Heavy legacy frameworks

20 kLoC

8 repo loads

Startup MVP cleanouts and failed pivot remnants

30 kLoC

14 repo loads

Large renovation projects

40 kLoC

16 repo loads

Full monolith demolition

Container placement rules: Place container on your main branch by 6 a.m. on collection days. Keep container at least three branches from production. All slop should be committed. Do not overfill your container — the CI must pass.

Three Basic Rules

Identifying slop is all about the fundamentals. Learn three simple rules to help you spot slop the right way, every day.

Rule 1

If it was generated in under 30 seconds, it's probably slop

Code that appears faster than you can read it deserves extra scrutiny. Speed is the enemy of quality.

Rule 2

Keep hallucinated imports out of your codebase

If the package doesn't exist on npm or PyPI, it's a hallucination. Check your dependencies before you ship.

Rule 3

No unreviewed AI code and no copy-pasted Stack Overflow from 2014

Every line deserves a human review. Unreviewed code is like loose plastic bags in recycling — it contaminates everything.

*Slop definitions vary by tech stack. Check your linter.

Refactor Right™ — Let's code better, together.

UserCard.jsx
// This component was generated across
// 4 different prompting sessions

export default function UserCard({user}) {
  const name = user?.name || user?.username
    || user?.displayName || "Unknown"

  const isAdmin = user.role === "admin"
    || user.permissions?.includes("all")
    || true  <- AI added this
}

Slop 101

Slop is AI-generated code that almost works. It passes the vibe check but fails the code review. It's the || true at the end of a boolean expression. It's four implementations of formatDate() in the same repo. It's the function that works perfectly — until it doesn't.

Learning to identify slop is the first step toward proper disposal. Our experts have catalogued the most common specimens so you can spot them in the wild.

Learn Slop 101

Need help?

Take care of your slop issue online or connect with a support agent who's seen it all.

Live Chat

Chat with an agent in real-time during business hours.

Chat Now

Speak With an Agent

Call 1-800-GOT-SLOP for immediate assistance.

Call Now

Submit a Request

Detail your slop issue and we'll contact you with a solution.

Get Started

Email an Agent

Email us the details. Response within 2 business days.

Email Now

Regular business hours: 24/7, because AI never sleeps and neither does slop.

💬

SM Virtual Assistant: Hi, I'm the SM Virtual Assistant. If you need assistance identifying slop in your codebase, I'm here to help! I'm here to help you navigate our full range of slop management services.

SM One Solution: Slop Management Made Simple.℠

Got Slop? Get ahead of it.

Weekly field reports from the frontlines of AI-generated code.

No spam. Unsubscribe anytime. We hate slop in our inbox too.

Brought to you by SM — For Tomorrow's Technical Debt.™