Building software products distilled: customer value, engineering and delivery
summary
Frames product, delivery and engineering around a central customer and argues XP-era practices still win: TDD plus pair programming (or mob) shapes design and reduces fear. Recommends domain-driven techniques—bounded context and ubiquitous language—applied to data mesh and internal platforms, with Kubernetes, event-driven integration and infrastructure as code as sensible defaults. Platforms must be self‑service products (example: Pleo platform team runs customer surveys) and teams stay small; consider platform economics before building.
AI-written summary · about
chapters (9)
- 0:00Building software products
- 1:04Software decision-making
- 6:08People in software teams
- 14:10Product and platform design
- 20:26Delivery obstacles
- 22:33Engineering practices
- 32:02Customers and value
- 36:16Platform boundaries
- 40:50Synthesis and closing
related talks
44mPlatform Engineering is All About Product
46mForget Developer Platforms, Think Developer Productivity!
33mWhy You Should Treat Your Platform as a Product
29mLet's call platforms what they really are, ways to provide something-as-a-Service
54mDeveloper experience platforms
36mApplying Product Thinking to internal infrastructure
43mEngineering Platforms Evolved
20mKeynote: Software Delivery and Developer Experience in the Age of Platform E...