Summary: I have started a government job as an intermediate software engineer, and the practices are very bad: no tests, no code review, we work without schedule. My manager is too busy and won't help with any changes. How can I improve the situation?
I recently joined a new team as an intermediate dev. I was worried about the recession, so I went from a startup to a government job and in terms of a paycheck I'm glad I did because the startup is laying off a ton of people.
However, it really does reflect many of the negative stereotypes about the government. There is no code review, very little unit testing, making decisions takes weeks, and we march along to a delusional schedule which just keeps piling more items into the new sprint and doesn't close the old sprint with the idea of finishing that sprint secretly. Realistically, we are two sprints behind where we officially are and haven't touched this sprints tickets, but on Friday will create a new sprint full of new tickets. We are simultaneously working on 7 open sprints...
We are behind because the lack of unit tests and checking leads to a lot of production bugs and we can never figure out our process of getting code to production and random features can suddenly become urgent without any real basis for it.
Another former Amazon dev says he tried to introduce changes, but they got blown away in a week as something broke and then the sprint needed to be finished. When I asked my manager about this all he had to say was "good luck". They've had high turnover, so I barely even saw him in the office as he was working on an urgent issue. I could take a week off spontaneously and I suspect he would be too busy to notice
I'm a month in and already demoralized. This job offers good pay, benefits and hours, but it's such a dismal environment. It's the first time I've wished that I knew how to be lazy...
Is this kind of thing worth trying to fix? Or will I just be making myself more miserable? How can I address these problems when management doesn't?