Developer Experience

AS_RZ_BIG_154 (1) AS_KRK_335 (1) (1)

Mystery of DX

The phrase "DX" is becoming more and more popular in the technology community, but its true essence is still unclear to many.

What exactly is it? Surprisingly, even Wikipedia doesn't provide a detailed explanation of what a developer's experience entails.

Join us as we set out on a journey to uncover the true meaning behind this acronym, starting with a concept that many of us are very familiar with - User Experience!
AS_KRK_334 (1)

First, let's talk about UX

In various sectors, from business and management to development, we all acknowledge the significant role that (UX) User Experience plays in the process of software creation. It's hardly surprising, given its roots date back to the early '70s with the advent of personal computers, and now every top-tier company hires UX experts. Creating a user-friendly, high-quality, and scalable application is nearly impossible without considering UX.


It's widely understood that overlooking UX leads to creating apps that are difficult to navigate and a hassle to expand and maintain. Keeping this in mind, observe how much ambiguity is eliminated from project development through the correct application of this small acronym. Many troublesome issues, such as those associated with project expansion, can be mitigated if we maintain a steady and mindful focus on enhancing the user experience.

What is DX?

Developer Experience can be understood as a special case of UX where the user is a developer.  This acronym came into existence with the rise of companies offering Software as a Service (SaaS) solutions.

To give you an idea, imagine creating a shipping service and offering an API. Your main users would-be developers from various companies looking to incorporate your service into their respective projects. A great comparison to understand this would be the differences between DE and PL DHL APIs.

Typically, the three core aspects of DX are highlighted: usability, findability, and credibility. These aspects align closely with the fundamental pillars of user experience. 1

AS_KRK_138 (1) (1)

Understanding the perspective

DX, or Developer Experience, encompasses the experiences of both internal and external developers when they interact with an application's API or SDK. Leading companies like Stripe and AWS prioritise DX, nurturing a community of developers and stakeholders to spearhead innovation.

Picture yourself as a developer in a bustling marketplace tasked with integrating a new shipping service every sprint, enhancing the functionalities of existing ones, and developing APIs for your clients.

In this role, you are responsible for implementing and maintaining integrations and facilitating the same for others. You find yourself frequently navigating through complex and detailed documentation, a task that also involves creating some documentation of your own.

However, DX goes beyond just documentation. It represents a comprehensive term that encapsulates a developer's entire experience, starting from their interaction with ticketing systems like Jira, to engaging with the ceremonies and artefacts of Agile methodologies and even down to the preference between light and dark modes in their Integrated Development Environment (IDE). It's about building upon past implementations and focusing on every facet of a developer's journey.

The importance of DX

Developers stand as the central pillar in the realms of software development and sales. Prioritizing their well-being and extending the necessary support is crucial. A positive DX not only enhances employee satisfaction and retention but also fosters the development of superior products. Moreover, DX perfectly complements DevOps, effectively bridging gaps in the software development life cycle.

Think back to a recent project where you observed developers being bombarded with too much information or, conversely, grappling with a lack of vital data. Instances where there was a heavy reliance on processes, a tendency towards over-engineering, or a misuse of agile methodologies.

A negative DX can spiral into a series of blame games, harsh repercussions for failures, persistent work overload, a hostile environment, diffused responsibility, unhealthy rivalry, and eventual burnout.

Addressing any or all of these issues can potentially bring about a significant improvement in various project facets such as eliminating knowledge silos, rejuvenating a demoralized team, curbing the "Not My Problem" attitude, bridging the gap between business and IT sectors, enhancing code quality, and reducing overall costs.

What should we focus on?

At its heart, DX is centered on crafting tools, processes, and environments that are specifically designed to cater to developers. The primary goal is to facilitate a workspace where developers can operate with efficiency, effectiveness, and above all, joy. A top-notch DX leads to accelerated development cycles, a reduction in bugs, and fosters a more united team.

AS_KRK_326 (1)

Intuitive Tooling: The daily tools, from IDEs to version control systems, should be intuitive, fostering creativity and efficiency.

Comprehensive Documentation: Clear, concise documentation is akin to a developer's North Star, guiding them through integration processes and potential challenges.

Community and Support: A robust developer community is a treasure trove of resources and support. Platforms like Stack Overflow and GitHub are a testament to this.

Performance and Reliability: In the software realm, efficiency is paramount. Lagging tools can stifle creativity and productivity, making reliability non-negotiable.

Feedback and Continuous Evolution: The software world is ever-evolving, and so should the tools and processes. Developers should have avenues to voice their input, leading to better tools and refined processes. This iterative improvement is the heart of DX.

Soft Skills and Advocacy: DX isn't solely about tools and processes. It's also about fostering a culture where developers can voice their needs, challenges, and feedback. By prioritizing soft skills, they can advocate for themselves and their peers, co-creating a superior DX.

Support Focus Time: Ensure developers have uninterrupted time for their tasks.

Reduce time-to-hello-world: Streamline the onboarding process for new developers.

Companies with excellent DX

1. Stripe

Example: Stripe's API and documentation are often hailed as the gold standard for DX.

Growth: Stripe's emphasis on DX has played a significant role in its rapid adoption by developers and its growth as a leading payment processing platform.
Community: The ease of integration and comprehensive documentation has fostered a strong developer community around Stripe, leading to more third-party integrations and plugins.

2. GitHub
Example: GitHub provides an intuitive platform for developers to collaborate on code, with features like pull requests, code reviews, and integrations with CI/CD tools.

Dominance: GitHub's focus on DX has made it the go-to platform for version control and open-source projects.
Acquisition: Its success and developer-centric approach led to its acquisition by Microsoft for $7.5 billion in 2018.
AS_KRK_293 (1)

Companies with challenges due to poor DX

1. Microsoft's Windows Phone
Example: In its early days, Windows Phone faced criticism for not being developer-friendly, especially when compared to Android or iOS.

Market Share: 
Windows Phone struggled to gain significant market share, partly because of the lack of apps on the platform.
 A less-than-ideal DX meant fewer developers were inclined to develop apps for the platform, leading to a vicious cycle of fewer apps, leading to fewer users and vice versa.
Shutdown: Eventually, Microsoft decided to discontinue Windows Phone.

2. Blackberry
Example: Blackberry, once a market leader, didn't adapt quickly enough to the app-centric ecosystem that iOS and Android were fostering.

Decline: Blackberry's market share plummeted as developers flocked to more developer-friendly platforms.
Transition: Recognizing the challenges, Blackberry transitioned from its own OS to adopt Android, but by then, much of the market share was lost.

AS_RZ_BIG_071 (2)


Positive DX:

Adoption: Platforms with good DX often see rapid adoption by the developer community.


Growth: A strong DX can lead to organic growth as developers recommend tools and platforms they love to their peers.


Innovation: With a positive DX, developers can focus on innovation rather than troubleshooting or navigating cumbersome processes.


Negative DX:

Reputation: A poor DX can tarnish a company's reputation within the developer community, making recovery difficult.


Financial Impact: Companies can lose significant market share and face financial challenges if developers abandon their platforms.


Long-Term Viability: In the tech world, where ecosystems are built around platforms, a poor DX can threaten the long-term viability of products or even entire companies.

In conclusion

DX is not just a buzzword. It has real-world implications for the success or failure of tech products and platforms. Investing in DX can lead to growth, innovation, and long-term success while neglecting it can lead to challenges and even obsolescence.
AS_KRK_218 (1)
Written by: Michal, on September 7, 2023
Developer Experience