What developers want
Download as PPTX, PDF0 likes703 views
The document discusses the key aspects of a great developer experience, emphasizing the desire for liberty, simplicity, and relevant tools. It highlights the importance of clear documentation, effective communication, and engagement with developers. Additionally, it underlines the need for authenticity, honesty, and empathy in interactions with developers.
What developers want
- 1. What developers want If Mel Gibson can figure out what women want, surely I can figure out what developers want. She said.
- 3. • SMS • Voice • 2FA • In-App Voice • In-App messaging
- 6. What I thought my job is!
- 8. What my boss think my job is?
- 10. What do developers want?
- 13. What makes a great DX?
- 15. Would you rather write this ?
- 16. Or this?
- 18. How about the tools?
- 19. Developers want to focus on solving a specific problem.
- 20. Speaking the right language
- 25. Developers want to use languages and tools that are relevant to them.
- 26. Documentation
- 27. This is for me All in one place
- 32. Developers want a clear structured documentation to help them understand and use your product
- 33. Communication
- 36. Developers want you to engage with them, ask them for feedback, help them with their questions and issues
- 37. Learning
- 42. Innovation
- 44. And most importantly Authenticity, Honesty & Empathy
Editor's Notes
- #5: What I do exactly at Nexmo? I’m part of the DevRel (Developer Relations)team , the advocacy team. We are the bridge between devs and product.
- #8: This year alone, I’ve been to ~20 conferences, ~7 countries, ~16 cities
- #12: DX matters for the same reasons good UX matters. Users of your technology are happier, promote it more, and stay longer when the product has good DX. Happy developers are chatty developers, and when we talk to each other to recommend products, the ones with the best DX are at the top of the list. Follows is my list of best practices when it comes to DX. Do these, and you’re well on your way to success.
- #13: Developer Experience (DX) is the equivalent to User Experience (UX) when the user of the software or system is a developer. DX describes the experience developers have when they use your product, be it client libraries, SDKs, frameworks, open source code, tools, API, technology or service. DX shares some ideas and philosophies from UX design (or HCI), but builds on these with an eye towards modern technology and standards.
- #23: Support different languages, target different platforms Provide SDKs, Client libraries etc.
- #29: Clear structure, code samples to encourage copy pasting , tutorials, guides
- #34: Great documentation leads to great communication. Communicate new versions of the product with good release notes, changelogs. Have clear README files .
- #35: Be honest and open when communicating with developers. The way you communicate with them determines how they perceive you and your product. Share your roadmap and let developers contribute.
- #36: There are many platforms to communicate with developers, help and assist them. Blog posts are a great documentation as well as an async mean of communication.
- #38: There are few ways to learn (visual, auditory, read/write, kinesthetic). Check out my friend Tomomi Imura’s talk for more details about the subject