Developer Experience Hi Paper Ver 0.1 Released: "Developer Experience: Exploration and Reshaping"

At the beginning of the year, I summarized some past experiences in platforms and open source software, and wrote the article " Developer Experience ". After that, I successively discussed the developer experience with people from different companies and different industries. Some are developers from internal platforms, some are related leaders from the technical community, and others are open source software contributors.

reason

From my feelings, the developer experience is an indispensable core element in the cloud-native era.

So, I began to think about how we built the development experience in the open source community, and wrote a series of articles: " technology product operation ", " document engineering experience design ", " document isomorphism: how to achieve Two-way binding of document and code? " and other related articles.

Developer experience is a combination of Developer + Experience, which is also its challenge-if we lack User Experience, then DX is not so easy. And if the people who follow DX are not from Developer background, then DX is not so easy.

In order to bridge this gap and no longer spend time explaining related concepts, I launched an open source project to write a booklet for the open source experience: https://github.com/phodal/dx , It adopts the CC-BY 4.0 protocol, you can modify and publish it freely, just mark the source and signature.

Why is it called Hi Paper

At first, I wanted to be a *paper method. For a better developer experience, I gave up the one-page e-book method commonly used in the past and used a more modular method to build this online document.

Therefore, I call it a happy book. On the one hand, it is for teasing, on the other hand, to make developers happy (after all, the main purpose is to revolve around the developer experience), and on the other hand to fill my initial Idea, so it becomes a book that is not a book.

Why is Version 0.1?

In the field of open source e-books, there has always been a concept of version, and the same also exists in the field of paper books. So, first of all, we must have the concept of version.

This is an e-book with only the core skeleton created, in order to expect more people to join the project. In the future, this manual can be released together through the community.

Compose mode

From the big subject classification, it is divided into:

• Five basic factors. That is, the five basic elements required by the developer experience: document experience design, error presentation, ease of use design, interaction design, touch points and support.
• Three models. That is, the developer experience measurement model, the fluency model to guide improvement, and the technical product operation to guide operators.
• Patterns and anti-patterns. DDDD (understand all that understand).
• Case study. Mainly used to provide a domestic analysis and communication platform in the future.

The core of the booklet is five design factors, which use definitions, principles, examples and patterns as the basic writing format.

future

Welcome to fill the pit~.

more is not helpful, please read online: 16185e1b1d5495 https://dx.phodal.com/

Source code: https://github.com/phodal/dx