Hacker News 👾
Назад к новостям
40
fagnerbrack•22.11.26 07:01

The Engineering Manager's role is under attack (again)

Источник
Комментарии
54

scott_w
22.11.26 08:07

Reading Meta wants a 1:50 ratio is wild. Let’s put some simple numbers down.I like a 30 minute 1-on-1 per engineer per week. At 1:50, 25 hours out of my 40 are now 1-on-1s.Assume a usual team is 5 engineers, so I’m covering 10 teams, effectively.So I have 15 hours to keep context of 10 teams. Am I expected to contribute as an IC, too? Usually when I’m directly leading a team, putting code into prod is how I feel the pain.Finally: am I getting 10x the salary for doing the job of 10 EMs?I’m all for cutting bureaucracy but is AI really this magical?

arnvald
22.11.26 07:52

I used to work in an organization where a senior director had 2 direct reports, one of them being a director who had 2-3 direct reports (senior managers), and these senior managers had maybe 3-4 managers each.Getting anything done was a nightmare because everyone up to the senior director level wanted to have an impact on the decision, so the approval process took ages.When done right, the flattening is good (and I say it as a middle manager) - it should remove layers that don’t add value, and empower people at lower levels. In this case removing the senior director or director wouldn’t hurt the organization.Unfortunately what I often see is that an organization will reduce number of people in one layer from 3 to 2, increasing the number of direct reports, but keeping the same number of layers leading to no improvements (besides cutting costs)

praptak
22.11.26 08:47

From my experience as a software engineer there is not enough management being done.I'm talking situations like broken processes that everyone complains about but nobody has the power to change. Planning cycles that stack delays. Unclear ownership where anyone can block your request but no one can approve it.I'm not saying this simply translates to "more managers". There obviously can be too many cooks. But I think currently we have too little and 50:1 is crazy, simply because 50 people cannot work as a single homogeneous group and you end up with TLs pretending they are not managers.

austin-cheney
22.11.26 08:17

At the last job I was managing 14 people (about 40% of the project), baby sitting the dysfunctional project manager, developing, and providing QA support for after hours deployments. I don’t miss it. I had too many bosses each with too many diverging goals.My number one goal when looking for the next job is to identify immaturity early. The result is I am still unemployed.

dcminter
22.11.26 08:06

The article makes a case that EMs do useful work but fails to make the case for why EMs can't be replaced by AI.

Animats
22.11.26 07:58

"One of the things managers repeatedly ask me about in workshops is: “How do I keep the team together when they prefer to talk to AI rather than talk to each other?”Now that's a new problem. Usually articles like this re-hash classic problems.(I recently had to chat with customer support for a retailer. The other end was human, and one of the better AIs would have been far more useful.)

matsemann
22.11.26 08:23

I've never worked a place where I've liked the implementation of engineering managers. Often it feels like the EM is both the tech lead / architect and your manager, which conflates things too much. Also they're often too busy to do either part good enough.I've much preferred when the managerial role is outside my team, or at least a different person. Makes it easier to discuss things with them.I'm not saying I don't value their work. Just that I don't like the way of putting multiple responsibilities onto one person.

fullstackwife
22.11.26 07:45

The article is from Sep 1, so still before Opus 5.5 release date, and I guess the mindset of authors was formulated long time before Opus 5 release, which I consider the turning point of software engineering industry. Things changed a lot since then, and it was a point of no return.

22.11.26 09:19

t43562
22.11.26 07:49

Developers do sometimes think they can do without managers until, as the article mentions, there's anything that needs deciding or a "people problem". It does make me laugh a bit that at each level there is a non-understanding about the adjacent levels such that destructive changes seem good at first glance.IMO it is valuable for people to occasionally do things out of their own area to generate that understanding but what business would ever allow that?