Developer Experience in Practice ![rw-book-cover](https://begin.com/_public/blog/post-assets/cole-dev-ex/analogue-life-japanese-scissors-ca64a66343.jpg) [[3. Resources/Readwise/Full Document Contents/Articles/Developer Experience in Practice|Full Document Contents]] ## Document Notes Many popular JavaScript frameworks market themselves as improving developer experience (DX), yet often deliver poor user experience (UX). This begs the question of if developer experience should be dropped altogether. Instead, it is important to consider why these frameworks are delivering poor user experiences, as there should be a focus on enabling developers to deliver reliable and first rate user experiences. To do this, developers should look to utilize the web platform and web standards, as these technologies have been around for decades and offer powerful techniques for great user experiences. This shift in focus would be an exciting developer experience. 1. What is the correlation between developer experience and user experience? 2. How can developers ensure they are creating reliable and first rate end user experiences? 3. What are the advantages of using web standards over other technologies? Abstract: This document discusses the concept of developer experience in practice, exploring the importance of providing an intuitive platform and user experience for developers. It examines the need for developers to have access to the right tools and resources to help them in their work, and highlights the benefits of ensuring a positive experience for developers. It also emphasizes the need to consider developer feedback and satisfaction when designing and implementing developer experiences. The document provides examples of ways to improve the developer experience and offers best practices for creating a successful one. Bullet List: • Introduction: o Overview of developer experience in practice o Importance of providing an intuitive platform and user experience for developers • Accessibility of Tools and Resources: o Need for developers to have access to the right tools and resources to help them in their work o Benefits of ensuring a positive experience for developers • Developer Feedback & Satisfaction: o Need to consider developer feedback and satisfaction when designing and implementing developer experiences o Examples of ways to improve the developer experience o Best practices for creating a successful developer experience Paraphrases: 1. Instead of simply creating a platform for developers to work with, companies should strive to create a positive experience for them. This means making sure they have the right tools and resources to do their job effectively and efficiently. 2. When designing and implementing developer experiences, it is important to take into account developer feedback and satisfaction. Taking their opinions into account can help to identify areas where the experience could be improved, and ensure that the end result is a positive one. This article discusses the concept of "Developer Experience" (DX) and how it has been marketed by popular JS frameworks to improve the experiences of developers, but often does not lead to an improved user experience (UX). The author argues that the focus should be on creating a positive DX that enables developers to deliver reliable and first-rate UX, and suggests that the web platform with its web standards and web components is the best approach for this. They suggest that web standards have been around for decades and are capable of offering powerful techniques for exceptional UX, and that more people utilizing these standards will help push them forward. > [!note]+ Document Notes > Many popular JavaScript frameworks market themselves as improving developer experience (DX), yet often deliver poor user experience (UX). This begs the question of if developer experience should be dropped altogether. Instead, it is important to consider why these frameworks are delivering poor user experiences, as there should be a focus on enabling developers to deliver reliable and first rate user experiences. To do this, developers should look to utilize the web platform and web standards, as these technologies have been around for decades and offer powerful techniques for great user experiences. This shift in focus would be an exciting developer experience. > > 1. What is the correlation between developer experience and user experience? > 2. How can developers ensure they are creating reliable and first rate end user experiences? > 3. What are the advantages of using web standards over other technologies? > > Abstract: > > This document discusses the concept of developer experience in practice, exploring the importance of providing an intuitive platform and user experience for developers. It examines the need for developers to have access to the right tools and resources to help them in their work, and highlights the benefits of ensuring a positive experience for developers. It also emphasizes the need to consider developer feedback and satisfaction when designing and implementing developer experiences. The document provides examples of ways to improve the developer experience and offers best practices for creating a successful one. > > Bullet List: > > • Introduction: > o Overview of developer experience in practice > o Importance of providing an intuitive platform and user experience for developers > > • Accessibility of Tools and Resources: > o Need for developers to have access to the right tools and resources to help them in their work > o Benefits of ensuring a positive experience for developers > > • Developer Feedback & Satisfaction: > o Need to consider developer feedback and satisfaction when designing and implementing developer experiences > o Examples of ways to improve the developer experience > o Best practices for creating a successful developer experience > > Paraphrases: > > 1. Instead of simply creating a platform for developers to work with, companies should strive to create a positive experience for them. This means making sure they have the right tools and resources to do their job effectively and efficiently. > > 2. When designing and implementing developer experiences, it is important to take into account developer feedback and satisfaction. Taking their opinions into account can help to identify areas where the experience could be improved, and ensure that the end result is a positive one. > > This article discusses the concept of "Developer Experience" (DX) and how it has been marketed by popular JS frameworks to improve the experiences of developers, but often does not lead to an improved user experience (UX). The author argues that the focus should be on creating a positive DX that enables developers to deliver reliable and first-rate UX, and suggests that the web platform with its web standards and web components is the best approach for this. They suggest that web standards have been around for decades and are capable of offering powerful techniques for exceptional UX, and that more people utilizing these standards will help push them forward. ## Highlights - Developer experience refers to how easy or difficult it is for a developer to perform essential tasks needed to implement a change. A positive developer experience would mean these tasks are relatively easy for the team. ([View Highlight](https://read.readwise.io/read/01gvx503r7j4b1kr70p6mkmqbj)) - Tags: developer experience - For a product to deliver good DX, it would typically need to be: • easy to learn (to help teams get up to speed quickly) • efficient (to enable tasks to be completed as quickly as possible) • consistent (to prevent teams from wasting time relearning how to do their work) • transparent (to allow bugs to be diagnosed and solved easily) • resilient (to ensure what works today also works next year) ([View Highlight](https://read.readwise.io/read/01gvx50q4p8a4v24dpe2ayhnsq)) - Tags: developer experience - Perhaps most problematic of all is the effect that contemporary developer experience has on educational programs (be they traditional classes, bootcamps, workshops, or anything in between). Such a rapidly expanding and ever changing technological ecosystem necessarily means that curricula struggle to keep up, and that the fundamentals of web development (e.g. HTML, CSS, HTTP, browser APIs…) are often glossed over in favor of getting students into the technologies more likely to land them jobs (like React and its many pals). This leads to an outpouring of early career developers who may speak confidently about things like React hooks or Redux state reducers, but who also lack any concept about the nature of HTML semantics or the most basic accessibility considerations. To be clear, I’m not throwing shade at those developers — they have been failed by an industry obsessed with the new and shiny at the expense of foundational practices and end user experiences ([View Highlight](https://read.readwise.io/read/01gvx531men8f2j61e5pe82n7n)) - Tags: developer education - Contemporary developer experience, to me, feels very much like we’ve been building websites with the code equivalent of Swiss Army Knives. ([View Highlight](https://read.readwise.io/read/01gvx576q6zccezdywaynajaa0))