The article honestly isn't that bad and has a number of interesting points to make. I recommend reading it rather than just dismissing it out of hand because of caricatures in the HN comments.
You can disagree with the article, but I think your parent comment is not a fair summary, e.g. w/ respect to bullets 1 and 2:
> At first, I thought, ‘This is a really unreasonable person.’ But later as I dug into it, I discovered he was right...This process of conflict mining served Larson a key lesson. “I could have just ignored him, But then I would have missed the key learning, which is that I was the one who was missing context, and needed to refine my approach.”
Maybe the parent comment was "conflict mining" itself. Often the quickest way to learn about something is to make a statement about it and then let others correct you if you're wrong.
On the other hand, "what is a power dynamic" is a fair counterpoint to that. Jeff Bezos, in contrast, said he generally withheld his opinion until the end so others wouldn't be afraid to contradict him; a powerful person sharing their idea can prevent others from sharing better ones.
A very good example of a ad social skill is to use provocative sentences and then wonder why people react to your provocation.
To play a charitable devil's advocate, here's my summary:
- You should have some understanding of what your people are working on.
- Suggesting a (potentially) bad idea is an efficient way to get people to teach you all the information you're missing.
- Rather than pinning down the perfect metrics, try to make do with the imperfect measurements that you already have. What do you want to achieve with those measurements? Focus on the end result (e.g., CEO understanding) rather than the metrics themselves.
- Don't sacrifice transparency on the altar of your shit umbrella. Protecting your team is good. Hiding things from them is bad.
I think these ideas could have been expressed better, to make them less easy to misconstrue. (I might be misconstruing the article in my summary! I'm honestly not 100% sure myself.)
If a toxic manager recommends this article and doesn't change their behavior, then that's definitely a red flag. They'll read anything and take it as vindication that they're doing the right thing.
Most IC engineers are cowards that refuse to give negative feedback about a peer even when it's anonymous. In order to really know how your reports are doing, you need to get down into the details with them. I've seen way too many low performer engineers survive for years just because their manager doesn't know enough about their work to know they suck.
At least that's how your summary reads to me.
The article is essentially arguing that the common management advice that circulates in our industry has caused too many engineers-turned-managers to pivot too far in the opposite direction from the caricature that OP created above, to the point where they've reached another ineffective part of the manifold of possible management styles. It argues that there's a space between OP's caricature and the traditional, ineffective engineering manager/executive and that in that space they can have real impact.
- Don't listen to people who tell you not to micromanage. You know better than your engineers do about how to do their jobs!
- Try to start fights. If it's not happening organically, manufacture some by heavy-handed prescriptiveness of cargo-cult approaches. What even _is_ a "power dynamic" anyways? Sounds made-up to me.
- Never question bad metrics. The company knows best! Except when you know best, at which point you need to involve the CEO in your team's day-to-day. They don't have anything else to do _anyways_, and your team will _love_ having the CEO hovering over their shoulders all the time!
- Never try to shield your team from bad corporate decisions. I mean, it's not _your_ problem, it's _theirs_ anyways!
This blog post was definitely written by someone who's lived in the cushy bubble of a particular flavor of consequence-free upper-level management for so long that they can no longer remember what the ground even looks like, let alone empathize with the folks digging the trenches.
If someone in management recommended this article, I'd take that as a red flag about their reporting chain.