I can definitely recommend this book for a (new) perspective on how platform teams fit into organizations.
In a past life I worked on an SRE team that backed up data to cassette tapes using a fleet of robots with lasers. https://youtu.be/kQ2taAttvwo That was easy. Hard SRE work is more like Traffic Team.
My personal view is that microservices, libraries, frameworks, apis, abis, etc. have a great deal in common today with how we've always thought about internet routers. Ask yourself this: if JavaScript web apps could run traceroute, then how many stakeholders do you think would show up before your query even reaches the wire?
So I think what the author Nick is saying makes perfect sense. Yes, these platform layers can cause difficulties. Can we fix them? Yes, just read the SRE book. That same wisdom will carry over just fine to this kind of problem.
“However, a number of factors are, and continue to, cause the traditional responsibilities of a Site Reliability Engineer (SRE) to shift.”
ie, SRE teams are shifting to become Platform teams or in other words are indistinguishable from them...
It's is a given that SRE build tooling, but most of the SRE-focused work, as described in that book is around improving the resilience of a given application or product. Addressing production readiness, defining SLOs, and handling incident response.
There are platform specific SRE teams at Google, but there's not much published about how they get about creating platform.
The book "Seeking SRE" makes it clear that in most places, the notion of "platform engineering" varies tremendously.
I don't know of any authors that have addressed this explicitly other than Susan Fowler in "Production Ready Microservices" who writes: