My experience with product managers is that they wedge themselves between the business and the technical teams and then wield political power while doing very little.
I'm currently trying desperately to get two different PM's to talk to each other so we can be consistent with permissions sets across two different projects. Both projects use the same set of API's.
One of the PM's is basically incognito, the other has actively been trying to avoid doing any of the work.
But the technical teams will get blamed for this, I know because I've watched these same PM's blame the technical teams for their own failings on other projects.
I'm with the article, fuck Product Managers, grab a senior developer and let him or her spend part of their time interfacing with business while also teaching the younger developers the skills necessary to do it.
The problem isn't that their responsibilities aren't useful, it's that there shouldn't be a role dedicated to their responsibilities, it immediately draws moats around everything and suddenly the need for communication and collaboration jumps through the roof because the people in that role don't understand the technology the way a senior developer would.
There's a segment of the developer population that wants to put their head in the sand, do their job, and clock out. These developers are low value and will never be able to take on the role described above.