Software is becoming increasingly easy to produce, so naturally people are producing more software. We're all just a few prompts away from turning vision into reality, and that is an enticing future to buy into.
The counterforce to this is that good software is still not easy to make, so most software being produced is "slop". Slop is software that looks functional but isn't. Slop is software that is fun to think about but painful to use. Slop is vaporware, software with no true form or purpose, built to monetize or build hype or follow trends but never to solve real problems. Slop is careless, unnecessary software.
Slop sucks.
And yet, slop is incredibly useful. Slop is useful because it represents the point at which ideas touch reality and most ideas, in their first iteration, fall apart when they're touched. An idea before it touches reality is mostly a convincing illusion, a fiction that is fun and perfect and safe from criticism.
Slop gives ideas substance. People should go out and build their ideas to test them against reality, as early and often as possible. Do you really want that minimal text editor you've been dreaming about all those years? Do you really need that new TODO system? That second brain? You might find the answer surprising and useful.
Slop is a byproduct of doing and thinking. As you build things, you learn. There's no better way to understand something than to build it, to touch the implementation details, to care about how the pieces fit together. You might find the slop disappearing, over time.
Good software is not the absence of slop. Well, it is, but it's not because good software was born pure and untainted. Good software works because it was built knowing what makes sense and what doesn't. Good software is beautiful because it was built knowing what fits and what doesn't. Good software feels cared for because it is, because it was sloppy enough for long enough that, eventually, it wasn't.