upvote
Middle-management as we knew it at the turn of the 2010s is probably gone forever. You don't need to coordinate many many teams as you used to. Same as huge frontend team with dedicated support for graphql, etc. AI made most of that redundant.

By extension we're going to need a lot less middle managers as coordination problems decrease.

As for the point I think you're trying to make, the problem with middle management and other chokepoints in general (like PM teams) is that often they become an antipattern. They soak in all the information and then dole it out parsimoniously, so the typical experience as an IC is to be barely able to see the full picture

reply
For the sake of moving this along, that describes me perfectly. Please, continue.
reply
Management advocates for AI because see ICs as commodities that just need to be coordinated to "do the thing." In this situation, remove the mid-managers, replace the ICs with AI, and use AI to enable them to coordinate the "workers." They forget that organizations exist to organize human output, which requires nuance, empathy, and communication.

ICs advocate for AI because they believe they are "doing the most valuable work." A rational AI would see that and let them do it. In this situation, remove the mid management, replace HR/marketing/sales/etc with AI and use AI to enable them to figure out what to build and they build twice as fast. They forget that the "rational" choice might not be what is best for them, their project, or their career.

Each one rebuts this with the way the system has failed them (managers feel that workers do everything BUT the work that moves the company forward, ICs feel like they can do everything BUT the work that moves the company forward)

reply
I have 35+ years experience as a manager and engineer at large enterprise tech companies (what the kids now call FAANG, though some of the company names were different back then), and was a Founder, CEO and CTO at a $7M VC funded company and several other "differently-funded" startups.
reply
Ha, excellent. I think you'll appreciate this then: https://imgflip.com/i/aswdth

I had a 50/50 chance of guessing which side of the bell curve you were on and I was wrong. :)

reply
[dead]
reply
Plot twist!
reply
Couple decades in with some leading but still remaining an IC officially.

The right work just doesn't get done without staff engineers and architect types having frequent conversations & meetings as well as constant code reviewing. Or long-term ICs effectively doing this role without the title and expectations/responsibilities (raises hand). You can identify these people because they ask questions relentlessly. Always well-considered ones, but even the ones that might make them look stupid in a meeting.

Coding is a small percentage of the work but also just as important. That's the sweet spot. The "non-stop meetings/socializing" people and the "headphones on & grind PRs" types are both two extremes of behavior that are boat-anchors in any organization and will bring productivity/customer-impact to a screeching halt if it goes unchecked for long enough.

And it's _always_ those stupid-seeming questions that uncover showstopping problems that would have bit you if left ignored.

Edit: Not to greenlight anything Palantir is doing, but in my opinion the FDE/FDSE model is probably everyone's near-future if your company is B2B. You can't be an "ignore meetings" type of person and do that.

reply
It’s a trap.
reply