When I first worked at Apple 30 years ago it was widely acknowledged that R&D had a two-tier system for software development. The rockstar engineers got to work on new stuff and the less productive/creative engineers cleaned up their mess. Bringing new features to maturity was a low-prestige activity and was not rewarded as well. The top engineers joined the hot new projects, shipped the first version, and then moved…
Sounds like just about every software job I’ve had over the last 7 years. It sounds like a mgmt problem to me. Either they can’t tamp down the devs who move too fast and break things, or they are driving the devs to do so.
"Hey, so you know how our application is pretty much always working, but will error out once every other blue moon? It does that less now," doesn't sound as flashy as "Look at this thing our app does that it didn't do before!"