After reading "programmer's professionalism"

This book is written by Robert Martin, a famous master in the Object-Oriented field. His first two works include Agile Software Development and neat code. The first part focuses on the design model. It uses a salary payment system to introduce the application of 24 design models. The second book focuses on writing easy-to-read and easy-to-maintain code. The first two books mainly focus on technology, and the book introduced here has risen to an improvement in the soft quality of programmers. It can be said that as long as we follow the master's work path, we can make rapid progress and improvement in our career.

Literacy this book runs through the book to talk about what is professional (professional), how to achieve professional. The reason why respected professions, such as lawyers and pianist, are respected is that they are professional and software developers are not professional. The book introduces how to make programmers more professional in various aspects. The most important thing is that professionals dare to take responsibility for themselves. Professionals do not undermine the structure and correctness of the Code. They perform test-driven and code refactoring. They strive to master the full knowledge of their fields, keep learning ahead, and practice diligently. At the same time, we are humble and good at cooperating to solve problems.

First, the masters let us know how to say no. In the IT industry, technicians often face a variety of pressures, such as time, changes, and uncertainty. In this environment, most people make rash commitments between face and pressure. In the end, the delay has repeatedly led people to doubt the professionalism of programmers. Therefore, the master recommends that professional programmers dare to say no, further dare to explain the cause of the failure, and fully expose the problem so that both parties can understand the result. Of course, the master did not let us refuse at any time, but at a high risk. At the same time, when you need to make a commitment, set a deadline for completion for yourself, and temporarily complete the deadline.

Second, keep your attention and energy in writing code. Do not write code when you are tired or upset, and do not listen to music when writing code. Do not let the brain enter the editing comfort zone. This way, although the Code is fast, it lacks global rationality. It should be interrupted in a moderate manner, but it cannot be interrupted frequently. Pair programming is an excellent practice for writing code. Tests are equally important as code writing. Traditional tests consume a lot of time, while TDD allows us to write test code before writing code, let's design and develop in advance from a testable perspective to ensure high cohesion, low coupling, and testability of product code. There is no good way to avoid working under high stress. Only by making good use of communication and others' help. At the same time, the principle should be maintained under pressure, TDD should be adhered to, and restructuring should be adhered. Rather than reducing some important practices under pressure.

Third, the estimation is different for the operator and the business party. The business side will regard estimation as a commitment, while for the operator, estimation is only an approximate estimation, which is not accurate and the accuracy of the estimation is normal distribution. Therefore, it is estimated that we should calculate the PERT Based on pessimistic and optimistic estimates to obtain a relatively more accurate value. At the same time, it is more accurate to divide a large task into small tasks than simply evaluating a large task.

Fourth, in terms of testing. From the product acceptance test and QA test system, the book involves. TDD, as the most basic part of testing, is an important guarantee for code refactoring.

Fifth, the programmer's time and energy are precious. It is necessary to use time management methods to plan and improve time use efficiency, while managing meetings and debates. To maintain energy, you must ensure good sleep and exercise.

Sixth, it is also a deep feeling for me, that is, practice. Masters talk about the feeling of a pianist practicing his fingers every day. programmers also need to practice every day to keep their brains and fingers agile.

Finally, for Team Managers, this book also introduces the importance of team formation and team member training and counseling.

After reading this book, I personally felt quite deeply touched. After I introduced it to my team members, everyone responded very well. Everyone realized that they were not professional, everyone is also willing to make themselves more professional, which can improve team morale and cohesion.