4 ms·
> But the lack on context means that those objectives are only loosely aligned with the direction of the underlying organisation as a whole I feel like this is
by Aeolun 4y ago
> But the lack on context means that those objectives are only loosely aligned with the direction of the underlying organisation as a whole
I feel like this is a failure of the organization, rather than of those managed.
I’m perfectly capable of prioritizing things correctly if given proper context, but chances are very real that I’ll still pay more attention to what is important 5 years down the line, rather than what will make manager X look good this month.
- laserlight 4y ago> I feel like this is a failure of the organization, rather than of those managed. Very much agreed. Indeed, this is the most important job of the management. Many comments speak of engineering as something that would go off track if left to their own ways. But, the reason for that is lack of context and wrong incentives, in the first place. If engineers don't know why they are not being allowed to work on technical debt, it's a management failure.
- xedrac 4y agoIt's simple enough to give ICs the correct context. The good ones, with adequate autonomy and purpose, will solve the company's problems in ways that will keep the machine running smoothly. That's not to say that every IC is good at prioritizing work appropriately. Some of them may go off into the weeds. But in my experience, it's much harder to provide context to management and business people, such that they truly understand the value of certain things. All too often, they march straight down a path that leads to pain, attrition, and gridlock, all the while, thinking they are maximizing efficiency. It's a story I've seen way too many times. Having said that, I have worked with two very effective managers. They were exceptional listeners, and knew when to compromise, and when to push back, on both sides of the fence. Interestingly, they were both former ICs and were very well acquainted with the technical side of things.
- HWR_14 4y ago> ’m perfectly capable of prioritizing things correctly if given proper context Probably, but how much effort does that take? Why are you duplicating that effort along with all the other ICs?
- gretch 4y agoHow are you so sure you know what’s actually important 5 years down the line? In the tech industry that’s a Herculean feat of prediction. You’re at Amazon, in 2001 and you know that in 5 years there will be a thing called AWS and that’s going to become the most important thing?
- gravypod 4y ago> You’re at Amazon, in 2001 and you know that in 5 years there will be a thing called AWS and that’s going to become the most important thing? Much of this is attributed to the email Jeff Bezos sent telling people to productionize internal APIs. My guess is: yes. People would be building what would have become AWS early on by solving the root problem for any given issue, establishing a decent API for it, and then consuming that API in some business logic. Bezos' big contribution was telling people to do what they would have usually done.
- ZephyrBlu 4y ago> I’m perfectly capable of prioritizing things correctly if given proper context A large part of a managers job is to have that context. Making everyone aware of wider context in a large org is untenable. ICs need to be able to focus on their immediate context so they can get shit done. There's a reason staff+ eng aren't writing code all the time. They need to focus their time and energy on higher level tasks that enable other ICs to write code. Personally I would love to have more context on everything, but I've got a glimpse of how much stuff my manager and PM are involved with and I definitely can't keep up with everything and also investigate issues, write code, etc.