Test developer experience, not code
summary
Advocates testing developer experience by verifying whether a first‑time integrator can answer “will this work for me” from the docs, measuring repeated questions (about 90% of new providers ask one specific connectivity question), and tracking those hotspots to prioritize updates. Internal docs include explicit dependency maps and detailed flows; external references stay search‑optimized snippets and a clear yes/no on support. Use lightweight diagram tools like Trovio or Lucidchart and an interactive Q&A that lets questions be rated and surfaced.
AI-written summary · about
chapters (8)
- 0:00Start
- 3:14How Can We Better Incorporate Developer Experience When Designing Apis
- 4:35How Do We Balance Complexity and Simplicity When Approaching Api Design
- 5:18Find the Right Api Reference
- 9:33Internal Apis
- 16:06Distinguishing between Internal and External Apis
- 18:11Peer Review
- 22:50Examples of Tools for Api Diagrams
related talks
14mDeveloper Experience: Your documentation deserves more love!
44mTesting Documentation: Why So Technical?
47mDesigning the Developer Experience
35mDev Experience in Technical Writing: 15 Tips to Boost Developer Satisfaction
39mDevelopers Documentation: your hidden strength
17mDevelopers Documentation: your secret weapon
35mBuilding Effective Developer Experience
24mDevelopers Are Users, Too