Sometimes, Lipstick Is Exactly What a Pig Needs!
summary
Argues that interface choice, not just backend polish, drives platform adoption and gives four concrete decision axes: autonomy, contextual distance, capability skill, and interface skill. Maps interfaces (portal, ticketing, wiki, IDE plugin, code templates, CLI like kubectl, sidecars, APIs) onto those axes, explains when each succeeds or fails, and recommends treating APIs as the canonical capability with “lipstick” frontends chosen to match user skill and flow rather than one-size-fits-all.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 0:21Platform engineering groups
- 0:50Focusing on interfaces
- 1:28Defining the interface
- 2:09Random capability pairing
- 4:37Autonomy and self-service
- 6:04Ticketing as an interface
- 7:11Contextual distance
- 8:09Optimizing for flow state
- 8:57IDE plugins and human help
- 10:29Code templates
- 11:41CLI for experts
- 12:40Invisible interfaces
- 13:17Documentation in CLI
- 14:10Interface skill levels
- 14:42Web documentation
- 15:21Recap and key concepts
- 16:55The role of APIs
- 18:40Conclusion and Q&A
related talks
42mIndispensable Principles for Designing Complex User Interfaces
26mThe "I" is for Interaction! Applying a developer-centric approach to API design
32mLet's put U in UX!
34mUnderstanding UX (and UI) – a practitioner's perspective
27mPortals and Platforms, Two Ps in a Pod? How Good Interfaces Make for Good Operability
34mThe best interface is no interface
27mMisplAIced: Good UI Needs Good UX
29mThe Interface manifesto