SINFO Keynote - Technical Principles of Developer Experience (DX)

Transcript

1. Shodipo Ayomide | Keynote - SINFO, Lisbon, Portugal 2021 Technical Principles of Developer Experience (DX)
2. Shodipo Ayomide Dev. Relations Manager at Stack Overflow • GitHub Star • Cloudinary Media Developer Expert • Community Evangelist Twitter & GitHub @developerayo
3. What is Developer Experience (DX)?
4. Developer experience (DX) is similar to how you see and understand user experience (UX) but the difference is DX focus is strictly on developers who consume certain API services, SDKs, or other services owned by a company or an organisation.
5. We help developers feel awesome and great about their work, because the transition into docs to product use case was easy.
6. Popular Question: Who is a Developer Advocate? 1. Technically Advanced 2. A Community Builder 3. Expert Communicator of Technicalities 4. Can Sell Software to Developers
7. User Experience (UX) is how the general users use your platform and their experience from loading up the first screen to signing up so routing to their dashboard.
8. Developer Experience (DX) is the flow developers have while trying to implement or configure your dev SDK, API, or your NPM package.
9. The difference: Developer Focused | General User Experience Focus.
10. Developer Experience is Value & Time Value - I can reach my goals with this API - This API provides even more than I need right now, exciting! Time - I can reach my goals in a shorter time - This API docs is amazingly straightforward!
11. Productivity of developers is measured in DX based on how fast developers move from docs to implementation.
12. Documentation
13. No docs, it’s simply called, I built this I don't care figure it out yourself, I hate stress 😬
14. The most important part of writing good docs is the structure, everything should be tabled properly and super easy to find.
17. Everyone love a well structured ReadMe
18. What happen’s under the hood when there is no docs:
19. Developers need to understand how your API service works, what endpoints are available, how to implement them, All these are great developer experience because it helps developers move from your docs to getting their api key/tokens to implementation.
20. Tools for helping with docs: - Docusaurus (JS) - Documentationjs (JS) - Gocco (GO) - Slate (Ruby) - Codex2 (PHP)
21. Documentation is not just for the end-user, you need it also, you are human, you forget things.
22. Commit Messages
23. Commit messages are part of documenting your code also. Which helps in improving the flow of onboarding new developers to the dev team,
25. Developer Experience Feedback Can be hurtful but it helps to improve the product. Any feedback is good feedback ✅ ❌
26. ImageHive.co
27. Thank You! Questions? You can also follow and reach me over on: Twitter: @developerayo GitHub: @developerayo Shodipo Ayomide | Keynote - SINFO, Lisbon, Portugal 2021