And many employers now require you to code faster, which is only possible with AI tooling. They don't understand that coding faster isn't always better.
Is this related to what business your employer is in? In other words, is their business producing code, or is code written to support some other business?
Everywhere. Normally adding an extra endpoint to the REST API would take a sprint. Now PM expects you to do two. Only way to get that done is a lot of vibe-coding and delivering sub-par results.
I am amazed that anyone ever needed a "sprint" to "add an endpoint".
It usually speaks to the approach you are taking, but I also believe sprint-based planning leads development teams to make work fit into it instead of needing natural time to do it.
Let's remember that all of have probably built full systems over a weekend. What organizational dysfunction has led to us needing a sprint is what needs fixing.
Of course they do. Generally the end result from this is bad - reduced in scope, buggy, and/or unstable. But that's an issue with communication/expectations/management. It'll keep happening either because of politics or the fact that a sub-par deliverable still meets the needs of the overall organization. Until it doesn't.
Or is this just everywhere now?