I wonder what would happen if you sent this nearly verbatim to executive leadership. It is quite a thorough, candid description of a serious problem.

At least I certainly wouldn't be happy to learn that my product was bursting at the seams and nobody was being held accountable. But I'm not an executive leader. (Maybe that's why?)

All of these issues were at some point raised to leadership. I've spent a lot of political capital on the issue and decided that it's not a hill I'm prepared to die on. Either a crop of new hires will come along and improve the situation with their fresh-eyed optimism, or it'll just keep happening and I'll try to remain zen.

And there's certainly a calculus to it that changes when you're an executive. To me, craftsmanship, diligence, and engineering excellence are important, not just because I love programming but also because I'm an IC and it affects me directly. To an executive, I am just some weird nerd they have to pay a lot of money to make computers do things. Beautiful code and a serene on-call experience are nice but they don't usually get a company acquired.

It probably doesn't worth it, considering it might impact the replier's career negatively. I'd never do that. I'd speak to my manager and if he just gets by then I just get by.