plus: * Put them oncall on Xmas when they are new to the team (because teams are like army where the newcomers must suffer) * be pedantic and hysteric in code

plus: * Put them oncall on Xmas when they are new to the team (because teams are like army where the newcomers must suffer) * be pedantic and hysteric in code reviews * have meaningless processes that drag for hours. E.g. iteration planning that goes on for 2 days * enforce nebulous "principles" (e.g. anything by RC Martin) because manager that hasn't touched code in a decade went to a show of him and was "impressed" * have clueless architects design systems and processes. Specially anything microservices-related. * have lesser engineers run the teams and processes. The kind that is good in Public Relations but have little or no real skills * have id-politics matter more than anything else. E.g. most important problem this week being why women employees got a pink promotional cup and how is that discrimination * do not allow access to web mail and a gazillion other sites because "security" * do not allow local code (if you see this - run) and instead promote "dev" in remote controlled envs * foster a blame culture (who did that?) * foster a toxic culture where politics run the place * fire good engineers and keep the above mentioned Public Relations ones * have and promote managers that are good in gaslighting and not much more * work for managers and with colleagues that you'd advise your kid to stay away from because they cannot be trusted * hire titles with no real experience and many ego issues and push them hard through the ladder. Classic example PhDs straight from uni.