Managers who don't code or do architecture or expect to be in the code or understand their team's technical complexity. Say they have 6 direct reports. What do they spend their time doing that delivers value commensurate with their salary?
Ask HN: What do higher level engineering managers who don't code do all day?
1–5 of 5 posts
Re: Ask HN: What do higher level engineering managers who don't code do all day?
#2The good ones keep management above them from wasting the team's time. They eliminate distractions, control changes to requirements, keep the team from being jerked around by some sales guy's latest brainstorm. They're worth a lot.
Re: Ask HN: What do higher level engineering managers who don't code do all day?
#3The good ones keep management above them from wasting the team's time. They eliminate distractions, control changes to requirements, keep the team from being jerked around by some sales guy's latest brainstorm. They're worth a lot .
"Shit umbrella." Not the only useful role for a manager, but too often a crucial one.
Re: Ask HN: What do higher level engineering managers who don't code do all day?
#4Make arguments that a particular project needs to be invested in, but by using "business lingo" rather than "technical lingo"
Re: Ask HN: What do higher level engineering managers who don't code do all day?
#5Actually have their ass on the line when things go south.
Actually understand team members' skills and working styles (as opposed to the random noise in performance reviews, or what other people say about them).
Actually refuse (and quit if necessary) rather than do something unethical, or allow their team members to be treated unfairly.