7 Best Practices of Slop Coding

You’ve heard of vibe coding, but have you heard of slop coding?

Slop coding is when your code becomes such a magnificent disaster after vibe coding that it makes absolutely no conceptual sense to the prompter—but that doesn’t stop them from continuing to burn tokens on a project that should have been scrapped three iterations ago.

It’s so delightfully chaotic you should definitely try it!

Here are my top tips to transform your vibe coding app into a beautiful mess of spaghetti nonsense in no time:

The Golden Rules of Maximum Slop

When your app breaks, gaslight the AI. Simply tell the LLM to “try harder” or “make it work better.” Bonus points if you add “please” or threaten to unplug the AI.

Master the art of incomprehensible prompts. Write requests so vague that even a human with a PhD in mind-reading couldn’t decipher them. “Make the thing do the stuff better” is a personal favorite.

Embrace the mystery. Never, ever ask the LLM to explain what it just did or provide feedback on your prompt. Understanding is the enemy of chaos.

Live dangerously without version control. Why save working states when you can experience the pure adrenaline rush of watching your entire project crumble with each “improvement”?

Go big or go home with changes. Make sweeping modifications to 47 different files at once. Testing incrementally is for cowards who actually want their code to work.

Stick with your first AI model choice. Why explore different models when you can blame the one you’re using for all your problems?

Ignore prompting techniques entirely. Few-shot prompting, chain-of-thought reasoning, and other fancy techniques actually work. Do you want to experience the euphoria that comes from fighting with the language model to get it to do what you ask, or do you want your code to actually work (borrrrinngg)?

Still Not Sloppy Enough?

If you’re struggling to achieve that perfect thick, creamy consistency of pure code slop, I’m always happy to steer you in another direction. It might not be a good direction, but it will definitely be entertaining. YOLO, right?

I’m only an email away: [email protected]

Remember: The goal isn’t to build software—it’s to create a beautiful disaster that future you will curse present you for creating. Happy slopping!