Building for Developers
summary
Clear claim: building developer products means optimizing for execution not glossing the topic. Presents concrete techniques: AutoDispose library with concise Gradle integration, test artifact and plugin for lifecycle testing; crash‑reporting reframed as stability jobs leading to features like automatic recovery and static analysis; customer segmentation as head torso tail personas to weight effort vs value; semantic versioning, deprecation signals and dependency hygiene to prevent runtime breakage. Examples include size budgets, CI + Maven distribution, and extension points that demonstrably reduce bugs and onboarding time.
AI-written summary · about
chapters (6)
- 0:00Introduction to DX
- 2:54Product strategy for tools
- 18:10API usability design
- 30:15Code quality standards
- 36:06Release management
- 39:35Community and engagement
related talks
27mDeveloper Experience: It’s Time to Start Complaining
44mBuilding for Developers
36mDeveloper Productivity Engineering: What's in it for me?
44mDeveloper Productivity Engineering: What's in it for Java Developers?
01mHow Do You Build For Developers?
30mAndroid Developer Productivity
43mDeveloper Productivity Engineering – The Next Big Thing in SW Development
48mTesting is Confidence - A Developer's Perspective
