I have seen such a story: Developers complain that customers are simply like pigs, because they don't use the software he develop or propose some weird demand. So his head told him: Ok, I agree that the customer is a stupid pig, then please do the software to make pigs can be used.
Customers are really stupid to this extent? I saw a few classic jokes about PC customer service, but I didn't touch it in actually. Many times we are dissatisfied is the customer's drill.
So our developers really need to develop the software that can be used by pigs? In fact, for developers, the importance of developing the process should be highly developed. Just like a wife, a harmonious and happy life is far more than a big fat child. Of course, if you can have a big fat child, it is very perfect.
While we fully emphasize the customer experience, have we taking into account our developers' experience? Exactly Is it developing this experience for the development process? Many times, many people will say no.
The starting point of the customer is totally different from our starting point. Don't trust the gods that "watch the problem on the customer's position". For requirements, we have to do this, but there are still many other important aspects of the development process.
The customer requires that we are very cool after you give the software. Because of many Chinese characteristics, "boss" always asks developers to try to meet customer needs, is to make customers cool, how much is our developers? It is estimated that many people have seen the programmer and prostitutes. Which developer has no feelings? But the streetwalker is different, we used the upper body to work.
We have sacrificed the developer experience.
The so-called developer experience is not high. Let developers go to the work he is interested in, at least he thinks it is worthwhile.
Obviously, another similar project development is not beneficial for developers. This is estimated to reconstruct this noun 's main cause of huge response in developers. I have started to use a wood like a wooden software, but now I am pinching with mud. What blocks us develop software in a more concise way? People's thoughts.
When we excited to use case driver, the model drives the architecture, "bosses" are still driven by interest. In fact, this is not strange, weird is that in their own head thinks that software development is physical activity.
There is definitely a smart technical supervisor will fully consider the developer experience, standing in the first line and fighting brain, said time is too tight, the budget is too low, require too high. But this reason is that ordinary developers can have no way to solve it. As long as you work, you can have this situation, especially in China, the project will always be more than the product. I can't solve this knot, at least now I can't solve, so I will put down.
The second reason is from our own. Tobecontinue
