Are you a professional software developer? -- Book Review: Emerging design-evolution nature of Professional Software Development

The original Article was first published in the Turing community. Http://www.ituring.com.cn/article/196

Many software developers are confused about their career development? Why are there so few reliable companies? Many software companies are confused. How can we recruit and train software developers and how to use them? Why are so few reliable software developers?

If you have any questions about what a professional software developer should look like, this book can be used as a reference.

1."Do not insult the peasant profession !"

"Do not insult the peasant profession !" -- The original saying is @ Meng Xiaolin Ralph. After reading the story of design-the evolutionary nature of professional software development, this sentence has always been echoed in my ears.

Software writing is a typical idea. There is a reference in the software industry. To become a master, you must have at least 100,000 lines of code experience first. As a result, the first goal of many software developers is to work toward 100,000 lines of code, which is the pursuit of thousands of "code farmers. Because software is writing code, it is the only proud skill of mass production software developers. But they do not like this only skill. For them, the sense of accomplishment of repeated code writing is very low, and the income is not high enough. Therefore, they have many 5-10 years of work experience, software developers with 2-3 years of experience have become managers or architects who do not write code. Another phenomenon is that the poor quality of the code they produce has plagued software companies and customers. They are called "coders ".

"Do not insult the peasant profession !" In most people's impressions, farmers are heading toward the loess. However, farmers are a respectable profession. In the agricultural society, the criteria for measuring a farmer are not whether he will play with agricultural tools, nor how many fields he has been able to cultivate. The criterion for measuring a farmer is the output of his farmland. Can these outputs support himself and his home. It is amateur farmers who only play with agricultural tools. Professional farmers need to cope with weather changes, observe crop growth, and take corresponding measures to ensure the harvest.

However, this is not the case in the software industry. The software industry is indeed different from agriculture, but the truth is the same. A software developer has only two criteria. One is his ability to play with various tools (the mastery of languages and tools), and the other is his work experience. In my career, I have seen several software experts who have harmed a company.

2.What is software?

The software industry is a magic industry. This industry basically does not discuss what software is, but is confident to do well in software. The software industry is a magic industry. Everyone in this industry can say that they are professional software developers. Ask yourself, do we really know what software is? Do you really know what a professional software developer is?

Some people think that software is code. The author believes that software is evolving in the book "design on the surface. I agree with the author's point of view. Software has been active since its birth. The business is its shape and behavior. The architecture is its skeleton, and the code is its flesh and blood. It needs to breathe and eat nutrients from the outside world, to be excretion, and to be a nervous system, software developers provide nutrition for each part of the body, such as hands and feet, and affect local growth.

Here, YY. The development of shape, behavior, skeleton, flesh and blood, nerves, digestion and excretion systems needs to be balanced. Over-providing local nutrition, the result of brutal growth is cancer. It is ridiculous to design a large-scale architecture. If you want to replace the original lime skeleton with a steel skeleton, You need to peel off the flesh and blood and replace the skeleton. At the same time, the flesh and blood are growing. Can the new skeleton and new flesh and blood work together? How can the neural system be connected, it is still unknown whether the overall shape can be maintained.

3.Are you a professional software developer?

If the software is active and evolved, what will the Professional Software Development do? We also need to learn from professional farmers to cope with weather changes, observe crop growth, and take corresponding measures to ensure the harvest. The author of design on the surface believes that even if we cannot guarantee that the software is evolving, we must at least ensure that the software is not degraded. First, you need to have a willingness to do nothing. Every time you modify the software, you should be careful not to make it worse. Then, verify the software with the user, and finally adopt a work method that can do nothing. Therefore, when writing code in amateur software development, professional software development will not make the software worse. Expert Software Development will make the software grow healthily.

How can we achieve this? For example, this is the author's suggestion. From a technical point of view, the author tells the technical skills required by professional software developers.

 

Is your software company plagued by software quality? Is your company plagued by the quality of software developers? We strongly recommend this book to the following personnel:

1) What is a professional software developer?

2) who want to become a professional software developer

3) individuals or companies wishing to develop professional software

4.The story behind

4.1Origin

There was a debate on Sina Weibo long ago (where Weibo's chronicle method was used. The topic is what emergent design translates? It is a variety of translation, emergency design, emerging design, evolutionary design, evolutionary design, emerging design, emerging design, what have. Seeing their heated discussions, I don't want to jump into their traps. As a result, several new Weibo posts described my understanding of the emergence and expressed my desire to read this book.

At the agile china 2011 conference, I finally got a book. It is quite comfortable to start with the book, and the cover is very concise. I think I still have a certain understanding of the emergence of design, I thought there would be no surprise, the results of a quick reading around an hour, cold sweat.

4.2Insufficient

1) Translation

The translation of the entire book is fluent, and the translator is still eager to read it. However, the translation of several key points makes people feel that they are not perfect. Emergent design is recommended to be translated into the emerging design, professional suggestions into the profession, and evolution suggestions into evolution. This translation is just a joke with my post-reading experience. Only such a translation can withstand repeated scrutiny and stimulate people to think more.

2) Title

Many it books are written on the name of the miserable book. I hope this book will not be missed. The title of this book is also bitter. When translated into a design book, it becomes a design book, a niche, with insufficient selling points. when translated into the evolutionary nature of professional software development, it becomes a philosophical book, not enough selling points.