(Your point is good, but the dig against MBAs is unnecessary and I wish it was less acceptable here on HN. It wouldn't be ok to make fun of people with Sociology degrees or History degrees here, but jokes about MBAs get a pass. We really should be better than that, but I realize I'm swimming against the current on this one.)
That aside, I have found a lot of clueless folks in tech leadership have that "furiously typing" misconception, as if developers are only productive when their fingertips are pounding keys. I once worked with a CEO who refused to set aside time in the schedule for things like setting up source control and a bug tracker, because he believed that developers should be furiously typing code in at all times.
The usual art student tropes are more offensive because they are about people in a chosen degree being dumb (incidentally, when I did engineering all the hardcore "haha artsies are so dumb" engineers failed out after first year). That's not the same as criticizing a specific flaw in their education. If there's some big blind spot the average sociology degree leaves, that should be fair game.
I struggle trying to educate people that the best way of measuring developer productivity is measuring outcomes, and that a developer going for a walk in the park is a great thing for them to do.
[0] In Australia, where management is generally still locked into 1950's-style authoritarianism. YMMV.
You're right. Ironically, I've seriously considered getting an MBA myself.
I changed it to "management-consultant thinking," which feels much more fair, given we are ripping on a McKinsey article in the first place. :) Thanks for the note.
99% of MBA's are certainly clueless about SWE because they never did SWE professionally.
It didn't seem to me like a criticism of MBA's fundamentally speaking.
Anecdotally, most of the MBAs I know are former coders. The last decade of Silicon Valley thinking it can reinvent commerce from first principles has massively increased the value and leverage of former coders with MBAs.
Of course an MBA is not the only way of acquiring those skills, but it is certainly an effective way. It can be incredibly powerful to someone with already strong technical skills. So I'd agree with OP that this trope is unwarranted and out of touch with reality.
edit: I like OP's edit, replacing "MBA" with "management-consulting thinking". Lots of old school consulting companies come up with recommendations for areas that they have no domain expertise. While it may look good on paper, it's a recipe for disaster, like the original article describes.
Does grate on me, though I might be biased, having worked 20 years in IT progressing upwards, and now looking at an MBA to round out my formal business education for further advancement.
But they keep coming across poorly on that metrics project.
I'm imagining their clients optimizing their operations, by bringing in management consultants, to tell them that the earlier management consultants need to be enabled to do what they do best: stay the heck away from sabotaging software development organizations.
And maybe the corporate $$$ optimization means real technology company will avoid this.
The irredeemable cynic might wonder if this is because they see themselves as the only ones who should be solving business problems.
So do most HN discussions about this. Look at how many people will say, “I’d rather be coding than in this meeting…”
Interestingly this is my distaste when I read pro remote-work posts about undisturbed focused time to do "the work".
I'm not saying it is intended or correct, but it is the implication I take from it, and I feel it undersells what engineers do
So, yes, you may hear about the sudden ability of people to get work done at a level they could not do when on site, and so they are happy about this aspect of remote.
It's been a couple of years since we went remote with our teams, and it has been a very positive experience for both collaboration and focus. We found that collaboration worked a lot better when it was actually intentional. It made the result of the collaboration more high value and strategic.
If you are depending on people accidentally bumping into one another for collaboration to occur, then you are being very poorly led.
> For example, one company found that its most talented developers were spending excessive time on noncoding activities such as design sessions or managing interdependencies across teams. In response, the company changed its operating model and clarified roles and responsibilities to enable those highest-value developers to do what they do best: code.
The rest of the article is equally hare-brained. It's a sort of clueless MBA thinking that believes software engineers should be furiously typing all the time, and it entirely fails to understand that actual software engineering is about solving business problems.
Stuff like this really makes me wish I'd optimized for $$$ earlier in my career, and I only hope I can retire before this kind of absurd thinking spreads into real technology companies.
[1]: https://www.mckinsey.com/industries/technology-media-and-tel...