Developer Experience

Written by Evaldo Junior (InFog) / Original link on May. 20, 2020

This post is about how one can help their colleagues being more productive and avoiding unnecessary work battling the source code they are trying to run.

User experience

User Experience (UX) should be part of our mindset as software developers, UX has the potential to be what makes a user continue to use a given product or not.

Good UX is about making the usage of a given product as easy as it can be, the user should never battle the product in order to get what they want.

Developer Experience

Developers on the other hand are smart people. Developers can go down a bumpy road and not even notice it.

Complicated development environment and hidden configuration files? Not an issue for a developer.

That’s why products focused on developers are usually unpolished, full of sharp edges and sometimes even enigmatic. This is to be sure that the real developers will keep the common folks away from those black screens and complicated commands.

Developers will even complicate a simple text editor to make it harder to use, all effort is valid to keep our world as peasant free as possible.



Developers need good experience as much as “regular users” do.

Being able to work on a project with guardrails and safe nets can make a big impact on one’s productivity and engagement.

This is where Developer Experience gets on the spotlight.

The products for developers are getting easier to use, see how easier it is to setup a cloud based queueing system vs running and maintaining your own solutions.

Frameworks and IDEs are going the extra mile to make building software easier, or at least making the start less scary and more welcoming.

We can and should have the same mindset on our own software. But how?

How to help

Here is a list of what you can do from today on to help your colleagues, your community and yourself:

Local development environment

Happy coding!



« Builders and architects: two types of programmers - Picking dependencies [blog] »