Complaining about technical debt is not just pointless, it's actively harmful. Stop it.
I get it. It's natural to be frustrated by all the cruft that is left behind when organizations grow and change, and there's often precious little effort spent to improve old codebases.
Here's the thing, though: Complaining makes it worse.
It's very easy to create a self-reinforcing negative feedback loop in a team when you complain about a previous technical decision. It's something everyone can relate to and rally around as being bad. We can all lament how we wish we had more time to clean up old things.
One of the biggest challenges in tech is getting people to work on the items in the @jnewland Magic Quadrant of important but uninteresting work. Jesse presented this model years ago and I've used it ever since to describe this phenomenon.
If you want to know why ops folks seem grumpy a lot, this is a big part of it. "If nobody owns it, ops owns it" is one of my favorite lines. This is one reason I like the "you build it, you run it" model of product ownership so much.
The SRE model also does a good job with SLO/SLI and error budgets. If you don't have strong feedback loops from production to help product teams value reliability, it can be difficult to even recognize important. If the problems are also uninteresting, you're basically doomed.