What is DX, or "Developer Experience"?

We're seeing more and more articles, tools, and resources of all kinds about DX, but what does that actually mean?

The acronym DX stands for "Developer Experience," meaning the experience of a developer when programming software (in the broadest sense of the term)

In other words, it's exactly like user experience, but focusing solely on the needs, the problems encountered and the solutions provided for developers!

Why is it important?

DX is a real topic that needs to be taken into account by everyone, and for everyone, from junior to CTO, because it influences two major aspects of our professional lives:

• Productivity
• Motivation

When a tool, a service, or a methodology saves you time, makes your life easier and reduces your mental workload at work, it quickly becomes something indispensable!

And therefore something you'll want to have, or set up, wherever you work in the future!

It's therefore a lever for greater efficiency, but also for recruiting, or retaining developers within the company.

A company, or a team, that hasn't evolved its development and deployment ecosystem in 10 years will have a harder time keeping its technical teams...

A concrete example

Let's take the deployment of a website.

For a very long time, the only real way to deploy a site was to connect via FTP, or SFTP, to the web server, and copy paste the files that had been modified to update the site!

Today, it's possible to host your code on a remote git repository, and deploy the update to a cloud hosting service in one click.

This is both a time saver, but above all it allows:

• Deploying more frequently
• Avoiding errors related to deployment (forgotten files, etc.)

DX, a real competitive advantage

If you develop tools for developers, then DX is no longer just an important topic, it's a vital one!

The ease of use, installation, configuration, and understanding of the tool will determine whether or not it gets adopted by an entire team, or even an entire company.

Some web frameworks are 2 to 3 times more optimized than their counterparts, and yet, they are far from being the most used on the market.

Why? Often because the resulting development experience doesn't measure up...

A few points to keep in mind if you're developing such tools:

• Pay attention to the first hands-on experience (the quickstart)
• The documentation
• The community
• Integration with other tools
• Plugins, and the ease of extending functionality in general

Here are a few examples of tools that are regularly mentioned, that are part of our daily dev life and with a great developer experience:

• Vue and Nuxt, getting started is very easy, and the documentation and community are incredible
• VSCode and its plugins, but especially Copilot which makes our lives easier!
• Git and GitHub (no need to introduce them)
• Clever-cloud for deploying apps in a single click, and which integrates directly with GitHub
• Strapi for generating APIs and having a back-office within minutes
• Notion for sharing knowledge

Choosing your tools well, or designing them well, when you're a developer, can have an impact that is sometimes greatly underestimated!