Enhance Developer Experience by community
summary
Community pair programming on Slack and Zoom surfaces a concrete surprise: developers read editor TypeScript hints, not external docs, so the backlog pivots from docs fixes to top-quality types that auto-document APIs. Practical tactics: run scheduled user tests via Calendly+Zoom, add a simple Google feedback form, dogfood builds, use friction logs from new hires, and reward the 1% champions (1% creators, 9% interactors, 90% lurkers). Examples include Format36 UI kits, Cypress error troubleshooting pages, and a docs+ChatGPT experiment at Stripe.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:28Five techniques for DX
- 5:55UX vs developer experience
- 9:54Developer vs user experience
- 11:20Jobs to be done for devs
- 14:49Key interfaces for tools
- 16:13What is developer efficiency
- 17:58Community improves DX
- 19:23Provide value to community before expecting returns
- 21:28Building trust in communities
- 23:53Rewarding contributors
- 25:19User testing with devs
- 27:45Internal community & dogfooding
- 30:15Summary
related talks
26mEnhance Developer Experience by community
35mAn introduction to developer experience, and the role of a documentarian
26mImportance of supporting designer & developer creativity
35mBuilding Effective Developer Experience
32mBuilt With Love - Why Developer Experience Matters
43mScalable Best Practices for Your Development Team
39mDeveloper Experience: How to Conquer the Hearts of Developers
35mDev Experience in Technical Writing: 15 Tips to Boost Developer Satisfaction
