Lessons Learned from 7 years of Running Developer Platforms
Submitted to Infobip Shift 2023 on . Accepted. Given .
This talk was given. See the talk page for slides, the recording, and (usually) a transcript.
- Level
- Intermediate
- Track
- Developer(Backend,API,Microservices,Containers)
- Tags
- Devops cloud PaaS kubernetes
Abstract, as submitted
This talk covers best and worst practices for Platform engineering. Who are you? You're in a DevOps, wait, I mean SRE...nope, scatch that..."platform engineering" team. People are coming at you to get kubernetes up and running and then build some kind of platform on-top of kubernetes. But you just got a build pipeline in place! Kubernetes may be a new, but building and running developer platforms has been going on for at least 10 years. This talk will cover the lessons those organizations have learned such as: product managing the platform, attracting and retaining developers, seeding trust and skills, re-skilling existing ops staff, and more. Examples are drawn from organizations like Mercedes-Benz, the US Airforce, large insurance companies and banks, and more.
This is the text that went into the CFP form, kept as submitted - not a later rewrite of it. Talks get retitled and reworked between submission and stage, so what was actually delivered may differ.
Notes to the CFP reviewers
Not part of the public abstract - this is what the program committee saw and the audience never does.
Thanks for taking the time to consider my talk!
The talk evolves each time I give it based on my new research, but here are examples of past versions:
1. Given with co-presenters: https://www.youtube.com/watch?v=gqKr-lK2Yyg
2. Given Solo:
https://www.youtube.com/watch?v=iSMtMlSNE_A&t=604s