because you are now getting coded products written in large by people who do not have technical foundations, so the way they interact with and even prompt the model is different. We all know how to fix this scenario; be more specific, or diagnose the abstraction mix ups and straighten those out.
Ask for change A and get unwanted change B happens all the time with bad programmers and tradgedy of the commons (ie poorly architected, no restraint) codebases.
Most normies dont know about this stuff.
Yeah, a while back I did a small project with a stack I wasn't familiar with, and it was really non-critical. So I decided to vibe code it. The experience was pretty similar to this satirical example. But when I work in areas in which I'm paying attention and understand the stack better, I don't experience this nearly as much