Personally, I found the article well written. Platform teams ultimately want the overall company to succeed. Their leverage - and mandate - is through helping the engineering org ship safer, faster, and more efficiently. The signal recommendations mentioned by the author are spot on from my experience, and I appreciated reading their perspective.
It IS hard to try to explain an alien concept to someone when you yourself in fact understand it.
I also don't think it's excusable to say it's hard for others to understand. The good SWEs I've worked with knew how to explain what they do to partner teams.
I understand it deeper than you think.even maybe deeper then author think he does.
The only singals that matter i already mentioned. Everything else must submit to this ultimate goal. If that’s the case there is no reason to invent anything even metaphorically speaking. And platform requirements arise naturally to exact extent the user problem justifies, not more not less etc.
This is probably a fundamental philosophical division between “engineers” who love to engineer for the sake of engineering, who are arrogant enough to treat their trade as an art form even.
And between mere mortals, regular engineers, who are hungry for solving real world problems as efficiently and quickly as possible.
Instead of figuring out the mess and navigating the peculiarities of another “platform team” in a big org.
because hn (the culture) rewards (with fake points) being contrarian.