3 ms·
It is understanding that leadership doesn't care about the technical details. Devs are expected to figure out these details on their own. Instead try to unders
by mobjack 4y ago
It is understanding that leadership doesn't care about the technical details. Devs are expected to figure out these details on their own.
Instead try to understand what others really care about and frame the discussions around that.
- sublinear 4y agoTechnical details are not always irrelevant nor mere implementation. They are often critical to the success of a product. It's like refusing to order from a menu at a restaurant and instead shouting "I WANT FOOD!" in a vain attempt to hide illiteracy. "Oh what kind of food, sir?" "GOOD FOOD! HOW DARE YOU ASK ME THAT!" "Would you prefer a picture menu, sir?" "...yes" So, better off talking to the product manager who just orders hamburgers for them. Of course that just drives a wedge between devs and leadership even further and erodes trust. No wonder devs job hop. No wonder every product is so mediocre. There's no escaping the fact that the days of non-technical leadership are numbered. Conversation should never be one way regardless of the hierarchy within a business. Such is the dysfunction of today's leadership.
- karmakaze 4y agoThis sounds like telling devs to 'manage up' which is shorter/searchable. I think that's good advice for more sr devs but juniors are still working out how to solve problems as stated and understood with their tech at-hand. Having this extra layer would probably be too much to deal with all together.