One effect doesn't exclude the other. I'm talking about people creating more problems than they are solving because they lack a fundamental understanding of how their systems, and the generated code that acts upon them, actually work. They're enamored with the ease and alacrity with which they can generate code but unwittingly leave a host of issues to be cleaned up. It's usually other people who discover the problems because these suddenly productive "authors" didn't have the know-how and awareness to create exacting enough prompts or sufficiently iterate on the generated output.

It's a phenomenon I've observed which doesn't necessarily take away from the benefits you've found. But maybe it's worth some consideration that this shift in empowerment isn't without negative consequences.

Have you built something you actually use? The feedback loop is immediate. You tell Claude and it goes it and fixes it.

You realize mostly proprietary software is made by people that haven’t even worked in that niche? Now people in that niche with these immediate loop can make software work way better and faster. Without the risk of it getting worse over time or selling out it a PE firm like Bending Spoons.