I’ve come to think a certain amount of attrition is needed to keep a product and the individuals working on it healthy. Back in my consulting days I worked with a few enterprise software companies that had a lot of highly tenured employees (think 10+ years). All the long-timers I met were skilled fiefdom builders with a strong bias toward opposing every change and maintaining the technical status quo because a lot of…
> All the long-timers I met were skilled fiefdom builders with a strong bias toward opposing every change and maintaining the technical status quo because a lot of their value was in their vast knowledge of the way things already are. So all German IT organizations? :)
My team was about 3 people (Americans, with our manager having worked in the German HQ for a few decades), who worked mostly on separate projects, and most of the headaches I had were due to change being opposed. I would try to do something, or request some sort of access to perform some task, and would get blocked by red tape that wasn't made visible until I was being told that I wasn't following a process that wasn't explained to me in advance.
There was one person whose sole task was managing the company-wide JIRA instance. If you wanted your team's board structured slightly differently, good luck. When I requested permissions to create a Component, the denial went to my manager instead of me, and I got a stern talking-to about 'the way things need to be done'.
On top of that, for a team of 3 people working on projects that are exploratory in nature, I'd expect that the local SQL server install (We didn't have the license key anymore, btw) would allow for us to have admin or developer rights. It originally did, until someone decided to change it, and I was the only member of the team who lacked that access.
I tolerated it for about 2.5 years (First job), but Covid gave me a great reason to quit!