There is so much going on in the tech world nowadays, new programming languages, new APIs and new tools everyday. Trying to keep up with all of it can be challenging. So how can we guarantee a smooth developer experience?
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.
This year alone, I’ve been to ~20 conferences, ~7 countries, ~16 cities
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.
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.
Support different languages, target different platforms Provide SDKs, Client libraries etc.
Great documentation leads to great communication.
Communicate new versions of the product with good release notes, changelogs.
Have clear README files .
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.
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.
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