"The Pragmatic Programmer - from small work to the experts," the first chapter study notes

This book, is teacher Wang Amway books. Opened the book, the book is written on everyone's praise and praise for. This book seems to be known as the programmer must read the book software engineering. I, as a sophomore software engineering, also began to read the book.

The first chapter, focusing on pragmatic philosophy. Overall, this part is some of the literacy requirement for a qualified programmer. Taken together is the case, a qualified programmer at least have basic responsibility, do not tolerate the presence of old code, and so on. Now I understand that my one by one these.

The first point to be responsible. This is either a programmer or other professional must have a good quality. We are all people need to do the project, the project no matter what position we are in, as long as we are a responsible person, the project is bound to be really up (if he got better, it must be someone else take on the responsibility you should take the ). Do not blame someone or something else, or put together an excuse. When the project failed to make up for the first time to think, rather than complaining about each other. Although I have no experience in project design, but which also contains the basic life principles. There's a great role for me.

Second, Do not Live With Broken Windows (Do not tolerate broken windows), the profound meaning of this sentence, not to ignore any part of the broken part of the code, the code to be responsible for the design of each part. In a project if each part of the code, decisions are very perfect, it would not have the heart to destroy the status quo.

Third, warm boiled frog brought us the truth, there are two things, one is to do a project catalyst, to make the whole project appears to have hope for the future. People do not give any idea of ​​the hopeless thing. While aware of the change in the mentality of everyone in the project, who otherwise in case of mind explosion, the entire result becomes very bleak.

Fourth, to make a good enough software, we must let the user involved. In other words, it is to make the decision to demand the function. Be the right medicine proper analysis of the needs of users and then through to the user's needs analysis. After the release of the demo version, but also timely issue, allowing users to perform adequate testing and feedback, the software can help you better progress.

Fifth, we should always pay attention to the latest developments within the industry, do not stand still. The computer industry has developed very quickly may be very popular today, after about a year of language it was hopelessly subscribers. After the find to the trend of development, we must promptly update their technology. To know the company is not support idlers, if a person can not keep up the trend of the times, then he is destined to be eliminated by the company.

The sixth point in the software development process, to keep the entire user communication between the team and the team with the team. Appropriate communication, but it allows us to run code and logic have been greatly improved.

Although read the first chapter, but I do not have any experience in development, these are still very lacking understanding, but also to understand the most simple point. In the future or to increase their amount of code ah.

Guess you like

Origin www.cnblogs.com/wushenjiang/p/11772783.html