Ask HN: When to quit company with bad engineering practices?
They are not a startup, they're well funded but everyone just do their own thing when it comes to code reviews, infrastructure architecture, etc. The infrastructure is really a mess and the code base isn't much different.
Teams spend most of their time doing manual things over and over and don't seem to understand how to find root causes, do problem management, etc.
I've focused on clarifying the reasons behind certain things so I could help to develop some standards, more documentation, etc. To at least avoid creating even more tech debt. People are drowning and doing adhoc fixes all the time.
Well, I've found it's really hard to get information out of the old timers. There's a huge focus on saving face, job security and not much concern about technical things.
I consider myself to be very polite and civil in discussions. I've worked with jerks before and I try not to be like that because I know people have feelings, etc... But I got some feedback that I should be "happier" in my emails.
Things are hard already and management is more worried about keeping the status quo. That's not what I was sold in the job interviews.
I'm close to saying enough is enough but I'm afraid this will be a mistakes, that I can still turn this boat around, etc.
How do you find out if you had enough?