Platform Teams Have Too Many Tools
tl;dr: There’s a new wave of platform tools and understanding what they are, when to use them, and how they differentiate is challenging. What’s a cloud development environment? How do you use platform orchestrators and Kubernetes? What does IDP even stand for? And how does all of this fit into a platform strategy?featured in #471
How Platform Teams Get Stuff Done
- Pete Hodgson tl;dr: “Platform teams have a unique reliance on other teams to ensure adoption of their platform - getting code changes into other teams' codebase is critical to their success. There are a variety of patterns for that cross-team collaboration, and selecting the right ones depends on both the phase of platform adoption and the ability of both teams and codebases to accept external influence.”featured in #433
How Platform Engineering Works
- Chad McElligott tl;dr: “I feel confident you will have a solid foundation upon which to build an effective Platform Engineering team if you follow these four principles”: (1) Set goals on outcomes, not outputs. (2) Truly know your customer. (3) Invent on behalf of your customer. (4) Scale your impact.featured in #426
The Future of Ops Is Platform Engineering
- Charity Majors tl;dr: "In the beginning, there were people who wrote and ran software. At some point, we spun away ops skills from dev skills into two different professions, but that turned out to be a ginormous mistake, so along came DevOps to reunify them. Nowadays, ops as an independent profession is in the process of fading out. Companies are spinning down their ops teams left and right. Engineers who formerly identified as sysadmins or operations have turned into DevOps engineers, and soon there will just be “software people” again. This is the way of things."featured in #361
What I Learned Building Platforms At Stitch Fix
tl;dr: "I was lucky enough to spend the last six years focusing on “engineering for data science” and learning to build great platforms." Stefan guides us through 5 lessons he learned: (1) Focus on adoption, not completeness. (2) Your users are not all equal. (3) Abstract away the internals of your system. (4) Live your users’ life cycle. (5) The two layer API trick.featured in #359
featured in #343