GoKawiilA couple of years ago, "slop" became the popular shorthand for unwanted, mindlessly generated AI content flooding the internet including images, text, and spam. Simon Willison helped popularize the term, though it had been circulating in engineering communities in the years prior.
At Greptile, we spend a lot of time thinking about questions like: Is slop the future? Are programming best practices now a thing of the past? Will there be any reason at all for AI coding tools to write what we call good code going forward?
I want to argue that AI models will write good code because of economic incentives. Good code is cheaper to generate and maintain. Competition is high between the AI models right now, and the ones that win will help developers ship reliable features fastest, which requires simple, maintainable code. Good code will prevail, not only because we want it to (though we do!), but because economic forces demand it. Markets will not reward slop in coding, in the long-term.
What's Happening Now?
Software development is changing fast. A prominent recent example comes from Ryan Dahl, creator of Node.js, who wrote, "The era of humans writing code is over. Disturbing for those of us who identify as SWEs, but no less true."
Meanwhile, the complexity of the average piece of software is drastically increasing. Theo [1] pointed out this trend. He notes that this increased complexity was driven partly by AI making it easier to ship more code faster, and partly by economic pressure for companies to keep up with competitors. Theo points out that the number of PRs are going up, which is what we've noticed at Greptile as well. As we covered in our State of AI Coding report [2], published a couple of months ago, lines of code per developer grew from 4,450 to 7,839 as AI coding tools became standard practice. Median PR size increased 33% from March to November 2025, rising from 57 to 76 lines changed. Individual file changes became 20% larger and "denser."
The stats suggest that devs are shipping more code with coding agents. The consequences may already be visible: analysis of vendor status pages [3] shows outages have steadily increased since 2022, suggesting software is becoming more brittle. Andrej Karpathy [4] describes: "agents bloat abstractions, have poor code aesthetics, are very prone to copy pasting code blocks and it's a mess, but at this point I stopped fighting it too hard and just moved on."
Collectively, software engineers are cranking out code at a high quantity. The approach driving much of this is brute force: generate code fast, iterate until it works, worry about simplicity and quality later (if at all).
Why "Good Code" Will Win
In A Philosophy of Software Design [5], John Ousterhout argues that complexity is the #1 enemy of well-designed software. Bad code needs lots of context to understand. Good code is easy to understand, modify, and extend; it also hides implementation details, and creates deep modules with shallow interfaces. This simplicity also holds practical implications.
... continue reading