News for hackers. Stuff that matters.
Re:Common Mistakes of New Engineering Managers by yaml-ops-guy on Wednesday March 17, 2021 @12:29PM (#26493406)
How have you found success balancing these things? It’s been my experience that managers of the first group eventually become unintentional members of the second group, even despite their best efforts to maintain productivity of their subordinates with intentional prioritization and grooming exercises because the business wants that new feature yesterday, and not getting it means lost revenue, angry customers and negative performance reviews.

What happens though when the business puts these types of middle managers in the impossible position of not being able to say “no, this isn’t a priority right now” but still expected to maintain the same amounts of engineering productivity and feature throughput?

I didn’t write this article, but it sums up my headspace, currently: https://www.linkedin.com/pulse/stop-doing-more-less-2019-mat...

Re:Common Mistakes of New Engineering Managers by Aeolun on Wednesday March 17, 2021 @08:15PM (#26498408)
> not getting it means lost revenue, angry customers and negative performance reviews

Staying in exactly the same place won’t affect revenue, customers or performance reviews at all. It’s when people work under the mistaken assumption that they have to increase at all costs that you have a problem.

Re:Common Mistakes of New Engineering Managers by SergeAx on Friday March 19, 2021 @02:37AM (#26510609)
> business wants that new feature yesterday, and not getting it means lost revenue

That's just plain bad planning on a business side of the company. They should either fix that, or face gradual departure of their workforce, from best to mediocre.