Incredible. Lately, I’ve been going through a bit of an identity crisis. I know I’m a passionate and not-so-bad developer, but with all this talk about AI, I couldn’t really understand if that was an end of an era for me.

But while reading this article, something clicked, it makes so much sense. It really made me feel better.

This is by far the best definition of AI slop I ever read, and the blog post itself is the contrary of AI slop: a short post where each word matters. The creation of an output that is at the same time large and lacks fundamental motivation/understanding is what creates AI slop, not the use of AI itself. This distinction allows us to have a mental model to don't blame AI itself but its continuous misuses. This also creates a formal model to understand why continuous AI steering during AI-assisted coding is so important. The sum of all the prompts provided, if they form a cohesive view of the software intent, constitutes the seed and specification that can generate good, useful code. Try to put together instead the sum of all the short prompts that prey the AI to retry "it does not work, retry", and see what you obtian.