Many companies invest in DX (developer experience) to raise developer productivity. But sometimes they try to do only “cool things,” or get so focused on making rules that they miss the essence of DX.

I think the essence of DX is in “making it so that you don’t need to know what you don’t know, and making it so that you can know what you know.”

To spell that out a bit,

1️⃣ Make it so you don’t need to know what you don’t know

Beginner or veteran, when using a system there should never be a moment of “if you don’t know this, you’re doomed.” The most common mistake is “rules that developers don’t know about coming into existence.”

Developers can’t always know every internal behavior, and they should be able to work safely without knowing. Basic mistakes and errors should be blocked by the system itself, and strange usage should not be encouraged. What makes this possible is proper abstraction.

A well-made abstraction hides the complex internals and exposes only what must be known. It gives the confidence that “you just use it like this.” Thanks to that, mistakes go down, onboarding gets faster, and the stability of the whole system goes up.

2️⃣ Make it so you can know what you know

If understanding a system or code requires “intuition” or “experience,” a major obstacle to productivity has already appeared. The more tacit knowledge there is, the more only those who know will know, and everyone else wanders.

Situations like “that’s just how it’s done” or “so-and-so wrote that, so you have to ask them” are the result of failing to share knowledge. DX lies in reducing this tacit knowledge and exposing information explicitly so that anyone can understand and grasp it quickly.

Revealing intent and making the flow traceable through logs, documentation, code structure, naming, messages, and so on, showing where something went wrong and how the system is running right now, is one of the core roles of DX.

In the end, I think DX should focus on “making work run smoothly.”