So just saw an email from our team's vice manager about need to improve code quality by using some new system.

Well that set me off on a huge rant about all the issues I see in my team and what exactly needs to change... (just some new sytem he's pushing isnt going to help)

wonder if i might get fired... even though i m right...

And so much for my plan to update docs... I've forgot what I wanted to do...

Most changes do not address the real issues, because that would immediately increase workload (although it could reduce it in the long run).

Changes are often made just so someone can say things have changed, but in reality, everything stays the same, just given it a new name.

I've seen that half a dozen times over the past years.

@ddephor it all comes down to technical debt. The short term fix assumes whoever is here now is gone tmr n it's someone else's problem.

So far though I m stuck here so most likely and is already... my problem.

Others as well but they don't realize it... To them it's just more work... Not work that could've and should be avoided.

An agile team where 30%+ of time and open tickets are devoted to fixing issues in Prod....