Behind the Curtain
About Slopapalooza
A field guide written by people who like AI coding and want it to actually work.
Slopapalooza is a field guide to the most common ways AI-assisted development turns into a mess. It’s satire on the surface — a fake festival poster, a list of fake band names — and a real engineering argument underneath.
The argument is one sentence:
AI coding does not remove the need for engineering process. It increases the penalty for not having one.
What “Slopapalooza” actually means
Think of a spectrum. At one end are teams not using AI at all — slow to adopt, actively resistant, or convinced it’s dumb because they haven’t seen how capable it’s become. Past them are teams experimenting in a measured way. And then there’s the rare team doing real agentic engineering: moving as fast as the tools allow while still shipping work that’s trustworthy enough for production. Fast and disciplined.
Slopapalooza is the other extreme — all the speed, none of the trust. It’s not a team that hit a few anti-patterns. It’s a whole organization where the anti-patterns are the operating model. The key thing: what separates that rare disciplined team from Slopapalooza isn’t how much AI they use. Both use a lot. It’s discipline. This site is not an argument against AI — it’s an argument against AI without engineering.
How a team gets there
The recipe is specific, and increasingly common. Senior leadership is gung-ho about AI. The technical bench is thin or too junior to push back. Agentic tools — not just chat assistants, but coding agents — get put in everyone’s hands, wired up with broad production credentials, and pointed at the goal with a single instruction: just get it done. No specs, no review bar, no acceptance criteria. Velocity is the only number anyone watches.
And here’s the trap: it looks fine on day one. No breach, no outage — code is shipping, demos land, leadership is thrilled. Underneath, it compounds. Every undocumented decision and 9,000-line component nobody understands becomes the starting context for the next change. The mess feeds the mess. Then comes the day of reckoning — the breach, the outage, the migration that can’t be rolled back, the departure of the one person who sort of knew how it worked. The deferred bill gets paid all at once, with interest, at the worst possible time.
Why this site exists
The same patterns keep showing up in engineering orgs that have leaned heavily into AI-assisted development without leaning equally into engineering discipline. The result: code nobody owns, nobody trusts, and nobody can safely change. The 9,000-line component is a joke, but it’s also a real thing that happens in real repos.
Slopapalooza tries to make those patterns memorable enough to be recognized — ideally before they ship.
The serious version
If you want this argument without the satire, the un-ironic version lives at Enterprise Vibe Coding. Same thesis, different costume.
Get in touch
Got a horror story, an anti-pattern we missed, or a correction? Send us a message — it goes straight to a real inbox.