1:14 Step 3 is probably the most important one. I have been doing Platform Eng years before we gave it name, and I can state enough that: Successful Platform engineering is done (most of the time) by talented product devs but with different Customers base (developer), with a clear goal of making THEM productive by clear quantifiable metrics (I challenge you to quantify the cost of being wrong!) But more often than not, companies rebrand SREs; it is the fastest way to create the biggest and most costly mistakes ever. SREs are extremely critical, but PaaS and IaaS are two completely different set of problems and required different experience.
Platform Engineering should enforce cost control factors through some of its key pillars or some internal budgets for each individual project because developer friendly interfaces may excites developers to spin up/provision excessive resources on infrastructure side.
1:14 Step 3 is probably the most important one. I have been doing Platform Eng years before we gave it name, and I can state enough that:
Successful Platform engineering is done (most of the time) by talented product devs but with different Customers base (developer), with a clear goal of making THEM productive by clear quantifiable metrics (I challenge you to quantify the cost of being wrong!)
But more often than not, companies rebrand SREs; it is the fastest way to create the biggest and most costly mistakes ever.
SREs are extremely critical, but PaaS and IaaS are two completely different set of problems and required different experience.
Platform Engineering should enforce cost control factors through some of its key pillars or some internal budgets for each individual project because developer friendly interfaces may excites developers to spin up/provision excessive resources on infrastructure side.