News for hackers. Stuff that matters.
Re:Engineering Management by emailslacked on Saturday June 19, 2021 @04:54PM (#27564383)
The fallacy of all these books, advice, philosophical quotes, so called knowledge about people is that, it’s too bookish and often advice is impractical to implement.

I have been EM for 5+ years now. There are number of factors on which I have zero control. M1 and M2 are doing often have no power besides sprint, agile processes. For whatever reason people are inherently unhappy. I have seen this happening in 3 different companies.

Compensation is major factor in unhappiness. But, lately it’s also the work that makes people unhappy. No one likes to do Oncall or operational or migration work or deal with mess left by earlier group.

Almost every single engineer think that they know better. I see large disagreements and often grunting agreements. You can apply advice like this all day long , but if compensation and work items are not satisfying, team will be unhappy.

Now, don’t get me even started on the hiring. It’s bizarre practice of leetcode, every tom,dick,Harry copying large organization processes like Amazon and Google.

I am actually quite frustrated in my manager career as someone who is not new the management. I am thinking if director and above level roles are more IC type but have better control over their career. Middle management is powerless in almost every aspect as far as I can tell. Please advice if you know how to get better.

Re:Engineering Management by molsongolden on Saturday June 19, 2021 @06:29PM (#27565089)
Some people are inherently unhappy but also keep an eye out for unhappiness caused by misalignment, misunderstanding, or disengagement relating to feelings of disempowerment.

Compensation is important up to a point but nobody likes feeling like they are wasting their time and powerless to make positive change.

> No one likes to do Oncall or operational or migration work or deal with mess left by earlier group.

No one likes doing these things if they don't see the point, if there's no buy-in and the work is just a directive from above, if everybody feels like they are treading water and not making any progress, etc...

There are too many possible contributing factors to list them all but most solutions involve listening, communicating, and making small changes that compound over time.

Build teams that: make progress, understand why their work is important, have meaningful feedback loops.

Some good starting points:

[1] The Management Flywheel - https://skamille.medium.com/the-management-flywheel-c076f398...

[2] Work is Work (In which returns diminish) - https://codahale.com/work-is-work/

[3] Model, document and share - https://lethain.com/model-document-share/

[4] Why limiting work-in-progress works - https://lethain.com/limiting-wip/

Re:Engineering Management by packetlost on Monday June 21, 2021 @10:36AM (#27579598)
To kind of expand on this, I actually like doing on-call and operational work. I find it very engaging and rewarding in the right context. The last company I was at, lower management had so little power, and the company was so unwilling to move anywhere (fairly old ISP) that it resulted in nearly all of the senior developers being either frustrated or jaded. It was a really toxic environment.
Re:Engineering Management by ferryman on Saturday June 19, 2021 @05:15PM (#27564527)
I think the work factor is addressable to some extent. For example - my team was unhappy about working on a legacy , monolithic codebase so we pushed for rewriting it , convinced the leaders about the benefits and now are spending significant time on it.