Suif, you have a lot to learn my friend. First is speaking in such absolutes. The more senior I get, the more I realize there are often a multitude of reasons

Suif, you have a lot to learn my friend. First is speaking in such absolutes. The more senior I get, the more I realize there are often a multitude of reasons things are the way they are, and many times those are valid reasons, when seeing something that is broken. Taking a beat before pontificating and making a fool of yourself will save a ton of heartache in your career. When you see something so broken, ask yourself why? Then ask somebody else. Some highlights from my career: 1) Last guy got cancer in the middle of a build. 2) Last guy worked his way up from one man help desk to Linux guru over 15 years all on his own, but was so busy putting out fires, he never had the chance to improve things. 3) Project started out as a proof of concept and was intended to be torn down. 4) Due to government contracts, the system has to be maintained exactly as delivered, no labels even allowed, and obviously no IT staff(?!) To make spreadsheets. Everything was paper notes by operators. 5) Pure laziness and incompetence as you alluded to. All this to say, more often than not there is a good reason something is fucked up, finding out why may help you fix it (like in the case of politics, budget issues, firefighting, priorities, etc..)