You’ve seen it in your feeds. Developers making a public show of swearing off AI for a month, participating in “No Sloptober” like it’s some digital puritanical holiday. It’s a performative purification ritual born from a very real, visceral fear: the dread of losing our hard-earned technical competence to a machine that mass-produces mediocrity.
The fear is justified. The ritual is a joke.
Locking your tools in a drawer for a month doesn’t fix the fact that you never had a quality bar to begin with.
Let’s talk about the uncomfortable truth. Slop wasn’t invented by AI. Slop predates ChatGPT by decades. Ten years ago, we called it “copy-pasting from StackOverflow.” It was the intern blindly accepting the highest-voted answer without reading the documentation. It was hardcoded API keys, it was 500-line functions nobody understood, it was the impenetrable spaghetti code abstraction layers that collapsed under their own weight.
AI didn’t kill craftsmanship. It just made developers who never had any dangerously fast.
When you sign up for “No Sloptober,” you’re using AI as a scapegoat for your own lack of discipline. You’re saying, “If I just turn off Claude, my code will magically get better.” It won’t. If you lack the critical thinking to architect a system when AI generates the boilerplate, you’ll lack the critical thinking to architect it when you’re typing it out by hand in VS Code. Abstaining from the tool just makes you produce the exact same garbage at a tenth of the speed.
The real tension isn’t AI versus human engineering skills. It’s about using tools as a multiplier versus using them as a crutch. And the “crutch” mentality is exactly what these performative abstinence movements expose.
Slop isn’t a property of the machine. It’s a product of human surrender.
Think about the actual development workflow. When you prompt an LLM, your job doesn’t end when the text stops generating. Your job begins. You are the reviewer. You are the architect. You are the last line of defense. If the AI spits out untested, fragile code, and you blindly hit “submit PR,” the AI didn’t create slop. You did. You produced slop by abandoning your responsibility for quality control.
We’ve seen this movie before. The bitter old engineer complaining that the industry is changing, refusing to adapt, and giving the rest of us senior folks a bad stigma. They treat not using AI as a badge of honor, a way to signal their purity. But purity of ignorance is still ignorance. Times are changing, and the answer isn’t to run away from the most powerful tool we’ve been handed in a generation.
The game has changed. Adapt and grow. True skill maintenance isn’t avoiding the most powerful tool available; it’s integrating your engineering standards into how you use that tool. You need a rigorous AI workflow: prompt, review, test, refactor, verify. If you skip those steps, you’re manufacturing slop—the AI is just the factory you chose to use.
AI doesn’t create mediocre engineers; it just makes mediocre engineers faster. The excellent ones use it to multiply their impact.
If you’re genuinely worried about staying sharp, stop the performative abstinence. Don’t do “No Sloptober.” Instead, declare a “Quality-First-tober.” Use the AI. Push it to its limits. But refuse to merge a single line of code you don’t fully understand, haven’t tested, and don’t own. That’s real craftsmanship. That’s bending the machine to your will, rather than throwing the machine away because you’re too scared to face your own laziness.
FAQ
Q: Doesn't relying on AI actually degrade fundamental debugging skills?
A: Yes, if you blindly accept its output. But the cure for degraded debugging isn't tool abstinence; it's deliberate review. You still have to debug the AI's logic. If you aren't reading the code, the problem is your laziness, not the LLM.
Q: What's the practical takeaway for a developer who wants to use AI without producing slop?
A: Treat the AI like a brilliant but junior developer. Let it write the boilerplate, but you must act as the senior reviewer. Test, refactor, and architect. You own the final commit, not the machine.
Q: Isn't 'No Sloptober' just a harmless way to brush up on fundamentals?
A: It's a cop-out. Blaming AI for slop is a way for engineers who never had a quality bar to feel morally superior. You don't maintain fundamentals by hiding from progress; you maintain them by applying strict standards to the new tools.