No it's not, because that other article absolutely isn't reciprocal, for all the reasons I had already listed above [0], 14 hours before you even wrote this. If you had read the other article, you'd see it flatly contradicts this article. Over there the OP trots out rhetoric like "Hold Yourself Accountable/ Help With the Dirty Work/ Be an Engineering Management Ally/ Be a World Class Copilot", but here moans about (hypothetically legitimate) scenarios where the PM may temporarily have to shoulder a lot of the QA burden (or push back on the customer rather than blame developers, if the customer doesn't understand their own use-case).

Conversely in this article the OP makes cryptic hand-waves towards "As always with power balances, just be gracious... Know that there are implicit power dynamics that should be managed graciously... So, be a good partner...", but what they write feels like they only view it as a one-way partnership, and makes it sound like they don't care if the developers are getting the short end of the stick. Or, they're trying to make a faulty generalization from their personal experience to other orgs where developers and PMs report to different chains and have very different incentives, as again other people here had already commented [1] before your post.

Your comment isn't constructive, and it intentionally misrepresents what I had clearly already written above half a day before you posted it. Please don't do that again. [2]

And I didn't make a "suggestion", I critiqued the OP's absence of having actually written something genuinely reciprocal like they said they had.

[0]: https://news.ycombinator.com/item?id=36466224

[1]: https://news.ycombinator.com/item?id=36467921

[2]: https://news.ycombinator.com/newsguidelines.html