This presentation was recorded at GOTO Copenhagen 2024. #GOTOcon #GOTOcph
https://gotocph.com
Steve Smith - Head of Scale Equal Experts
RESOURCES
https://bsky.app/profile/stevesmithtech.bsky.social
https://mastodon.social/@steve_smith@mastodon.social
https://www.linkedin.com/in/stevesmithtech
https://www.stevesmith.tech
ABSTRACT
Why is it so easy to screw up platform engineering, and how do you undo the damage?
Platform engineering… it’s the trendy new buzzword. For a thing we’ve been doing for years, ever since someone said “what if we re-did Solaris zones, but called it Docker instead?” It means building an internal engineering platform for your digital services or data pipelines. It allows you to scale teams up and down, and supercharge their abilities to deliver outcomes.
But here’s a thing that nobody likes to talk about. It’s easy to totally screw up platform engineering. When that happens, there’s a huge negative impact on your engineering culture, and your teams aren’t able to achieve their goals. So how do you avoid screwing up platform engineering, and if it does happen to you, can you actually fix it?
I’ve spent years in platform leadership roles, building internal engineering platforms at different scaleups and enterprise organizations. I’ve had successes, and I’ve had failures. I’ll cover the following irreversible ways to screw up, and how to start reversing out of them:
• Power tools - teams spend all their time configuring Kafka, Kubernetes, Istio etc., because the platform is based on overpowered tech
• Technology anarchy - N teams do the same task in N different ways, because the platform has no opinions on tech choices, ways of working, or path to prod
• Teams as tickets - making teams interact with the platform via tickets
And I’ll explain why all of these can be traced back to a scaling problem, the granddaddy screw up of platform engineering - your mindset is platform as a project, not as a product.
Takeaways
• Platform engineering is about creating an enabler of business value, so your teams can move faster and safer than ever before
• Avoid using platform engineering power tools e.g. Kafka, Kubernetes, Istio. If you’re using them, start measuring unplanned work and plan to migrate away
• Avoid being unopinionated on tech stack, ways of working, and path to prod. If you’re doing that, capture your leadership team’s expectations and track team commitments
• Avoid only interacting with teams through a ticketing system. If you’re stuck there, start collaborating with teams on self-service paved roads
• The key to platform engineering success is a platform as a product mindset [...]
TIMECODES
00:00 Intro
03:36 What is platform engineering?
05:37 No. 1: Power tools
18:32 No. 2: Technology anarchy
31:18 No. 3: Ticketing hell
40:04 Takeaways
42:24 Outro
Download slides and read the full abstract here:
https://gotocph.com/2024/sessions/3235
RECOMMENDED BOOKS
Steve Smith • Measuring Continuous Delivery • https://leanpub.com/measuringcontinuousdelivery
Steve Smith & Denise Yu • A Children's A to Z of Continuous Delivery • https://leanpub.com/achildrensatozofcontinuousdelivery
Steve Smith & Matthew Skelton • Build Quality In • https://leanpub.com/buildqualityin
https://bsky.app/profile/gotocon.com
https://twitter.com/GOTOcon
https://www.linkedin.com/company/goto-
https://www.instagram.com/goto_con
https://www.facebook.com/GOTOConferences
#PlatformEngineering #PlatformLeadership #Kubernetes #ApacheKafka #Istio #TechnologyAnarchy #CICD #SteveSmith
CHANNEL MEMBERSHIP BONUS
Join this channel to get early access to videos & other perks:
https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/join
Looking for a unique learning experience?
Attend the next GOTO conference near you! Get your ticket at https://gotopia.tech
Sign up for updates and specials at https://gotopia.tech/newsletter
SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.
https://www.youtube.com/user/GotoConferences/?sub_confirmation=1