What Developers Want!
summary
Developer advocacy for a telecom API company focuses on remove friction: replace app.config auth with an instance-based NextMode client so C# users stop filing the same issues, maintain client libraries across popular languages, and push a v3 configuration release that cuts setup confusion. Team runs ~20 conferences across seven countries, publishes quickstarts and building-block samples, and claims 3 documentation awards. Documentation is open source, changelogs and automated release notes aid retention, and hackathons surface surprising integration ideas.
AI-written summary · about
chapters (12)
- 0:00Start
- 0:50Introductions
- 2:42What Is the Job of a Developer Advocate
- 17:52Languages
- 18:26Documentation
- 20:03Building Blocks
- 29:14Tools and Resources
- 29:29Ways of Learning for Developers
- 32:14Quick Starts
- 35:29Hackathons
- 36:24Innovation
- 50:10Internal Documentation
related talks
28mDevelopers are People Too! Building a DX based API Strategy
25mWhat Developers Want
27mGetting developers hooked on your API
19mKeynote: How to Win Friends and Reduce Tech Debt with Developer Experience
27mDemocratizing developer experience
24mBuilding Trust: Developer Relations Secrets for API Success
12mAnne Gentle, Cisco DevNet | DevNet Create 2019
25mDo you know who's reading your Docs?