I think their "platform engineering" does not bring clarity, it just redefines existing term weirdly.
For me, "Platform engineering" builds platforms, and they don't really deal with individual apps. Sure, they may answer your questions and they will evolve platform to support your use cases, but their ultimate output is a platform. Think Hashicorp or Amazon - even with premium support, they still expect you to write majority of .tf files / manage their resources.
"Devops" have many roles, and one of those is to interact with platform engineering and actually use their product, and write those .tf files. What author describes seems like 100% devops.
I think their "platform engineering" does not bring clarity, it just redefines existing term weirdly.
For me, "Platform engineering" builds platforms, and they don't really deal with individual apps. Sure, they may answer your questions and they will evolve platform to support your use cases, but their ultimate output is a platform. Think Hashicorp or Amazon - even with premium support, they still expect you to write majority of .tf files / manage their resources.
"Devops" have many roles, and one of those is to interact with platform engineering and actually use their product, and write those .tf files. What author describes seems like 100% devops.
https://xkcd.com/927/
doesnt really work when youre working on a paas though