3 ms·
Eng mgr at a FANG, was IC previously. The following is assuming the senior folks (managers or senior ICs) around you are acting in good faith. If you actually h
by gandalfgeek 4y ago
Eng mgr at a FANG, was IC previously. The following is assuming the senior folks (managers or senior ICs) around you are acting in good faith. If you actually have toxic senior people, that's a whole different scenario.
Managers have to balance two priorities, which are sometimes competing: promoting engineering excellence on their teams, and delivering value for the business. The most common example of a conflict between the two is taking on tech debt to release something earlier.
If you disagree with a leadership decision, try to get more background on the thinking behind it. Good managers will be more than happy to get into it in detail. There are always tradeoffs to be made, and the inputs are not always purely technical. There often are business and organizational constraints too.
This is often a barrier that ICs have to break through to get to more senior levels (even they choose to stay on the IC track): making sound engineering decisions, but also being able to understand the business and make appropriate tradeoffs.
- shallichange 4y agoSame boat but in big financial institution. How do you handle missed deadlines committed by higher ranks depending on your team’s delivery? In one word: failure? Hard to just “accept and move on” when the failure is not acknowledged and managed and plans are not changed in the company. I find myself trapped in that situation, and it follows me home. It sucks
- yuppie_scum 4y agoThis is it. Most of my employment conflict/disillusionment has come from the “do it now” vs “do it right” dilemma. And sadly in my field of DevOps/SRE, “do it right” is really what we are striving for so it can get pretty disheartening to start getting shot down for feature work over and over again.