4 ms·
Regarding tech leadership: Perhaps I've just been unlucky, but a rather depressing proportion of tech leadership that I have been under in the past appear to h
by samhuk 3y ago
Regarding tech leadership:
Perhaps I've just been unlucky, but a rather depressing proportion of tech leadership that I have been under in the past appear to have seeked the role in order to:
1. Hide lack of engineering aptitude.
2. Put less work in.
If i'm on the right track with that, then it well explains why they don't care about cultivating a good engineering culture and let everything devolve into a zoo - i.e. everybody feels like everyone is out to get each other, no team work, rep farming, and all that nonsense.
Regarding getting work done:
I agree, I actually believe that it's the cause of the slow death of many companies: A gradual acceptance of nay-sayers, laziness, and "losers", that is to say an acceptance of people who just think that everything is lost, there's no point to fixing anything, and instead choses to spend their time placating why nothing can be done about anything.
It's depressing, and was traumatic for when I was working in those environments in the past. (I like to think) I'm a get shit done and deliver awesome products kind of guy, so these "loser" engineers and leaders are a true PITA.
- hinkley 3y agoIt can be tough because a lot of the work I do that gets me or keeps me in a technical leadership position is building lieutenants. That necessitates me transferring ownership of things to them, so they can grow or at least demonstrate to the organization that they have adulting skills and need a raise. That can look a lot like me trying to do less work. Most of the time what I’m doing instead is looking at problems we “didn’t have time for” but are about to bury us. I can only juggle so many balls at once. What’s your favorite color? <hands you one>