The Developer Experience (DX) centric Organization structure

How are we defining it today?

New ways of working such as globally distributed developer networks will require a better understanding of developers’ feelings, perceptions, motivations, and identification with their tasks in their respective project environments. User experience is a concept that captures how persons feel about products, systems, and services. It evolved from disciplines such as interaction design and usability to a much richer scope that includes feelings, motivations, and satisfaction. Similarly, developer experience could be defined as a means for capturing how developers think and feel about their activities within their working environments leading to an improvement on team management and project performance.

Is DX restricted to documentation?

Everybody thinks good docs are important. There is no such thing as a technology that is better than another but has much worse docs. The one with the better docs is better overall because it has better docs. That’s not the technology itself; that’s the world around it. For instance, technology might be “good” already. Say it has an API that developers like. Then it starts offering a CLI. That’s (generally) a DX improvement because it opens up doors for developers who prefer working in that world and who build processes around it…