How to fix the Developer experience
•
2 likes•78 views
Developer experience (DX) refers to the experience developers have when using software or a system, analogous to user experience (UX) but focused on developers as the end users. DX encompasses the entire developer journey from signing up to debugging, including building, testing, and running applications or code. For organizations providing tools or platforms for developers, ensuring a positive DX involves open communication, guidance through documentation and tutorials, respecting industry standards, and maintaining an open source contribution process.
More Related Content
Similar to How to fix the Developer experience
Similar to How to fix the Developer experience (20)
Recently uploaded
Recently uploaded (20)
How to fix the Developer experience
- 2. Developer Experience (DX) Dakshika Jayathilaka Associate Tech Lead - WSO2
- 6. Developer
- 8. What is DX? the equivalent to User Experience (UX) when the user of the software or system is a developer
- 9. Who are you? DEVELOPER CONSUMERSPROVIDERS
- 12. Sign up
- 13. Signup
- 18. Getting Started
- 22. Build
- 26. Test
- 27. RUN
- 28. Debug
- 32. Guidelines - How to make it work
- 33. Authentic & Open Communication ● Honest with developers, they’ll respect your product more ● Honest about your timelines ● Communicate product roadmap
- 34. Guidance ● Guided flows/ Incontext help ● Documentation ● Try-out options
- 35. Respect Standards and Idioms ● Follow the industry standards ● Support for the tools ● Platform consistency
- 36. Open Source ● Safe Space for Contributions ● Open CI ● Makes it easier for you to review and accept or reject contributions
- 37. Q & A
- 38. Thank you
Editor's Notes
- Don Norman : Psychology Department at University of California, San Diego (UCSD) Design of Everyday Things. 1993 Apple + Job Title encompasses all aspects of the end-user's interaction with the company, its services, and its products
- All the interactions between developer + client libraries, SDKs, frameworks, open source code, tools, API, technology or service. CLI DX shares some ideas and philosophies from UX design (or HCI), but builds on these with an eye towards modern technology and standards.
- Take the Play store scenario - they away Main Two Aspects Websystem Stand Alone
- Getting Approval from the Human
- Take the Play store scenario - they away Main Two Aspects Websystem Stand Alone
- Tooling same tool that you used to develop
- Take the Play store scenario - they away Main Two Aspects Websystem Stand Alone
- continuous integration, a practice that focuses on making preparing a release easier. merge their changes back to the main branch as often as possible changes are validated by creating a build and running automated tests against the build make sure that you can release new changes to your customers quickly in a sustainable way Continuous deployment goes one step further than continuous delivery. With this practice, every change that passes all stages of your production pipeline is released to your customers
- data breach, a bug, a period of downtime, or some data loss honest about your timelines Communicate product roadmap with product forums, and let developers contribute to those priorities directly. Engage with them, ask them what they think
- client library, SDK, API What Xcode version are they on? different languages, but platform consistency --- > npm install Respect Platform Idioms and Toolsets - versions that they are using / tools etc Consistency
- more trusted by developers, more developers are exclusively using only open source dependencies able to look into the source and find and fix bugs Open CI - Most hosted CI systems are free for open source projects, so just hook it up and tie it easier to contribute with pull requests and makes it easier for you to review and accept or reject contributions