First, I read the preface, this book may now understand or can not read, but some knowledge of the book might help me in the future development of software to go the point of detours,
So, maybe I still do not understand now, but I would surely read as much as possible to understand some of the experiences and contents of the book, which I read this book demands on themselves.
begging.
Then I read the first chapter, the first chapter, while small space, but overall still gain a lot of reading down. In the beginning of the first chapter, it taught me to do a
A principle to do a programmer, that is honest and responsible. If you do something wrong, admit it, and gives the selected remedy, not to pass the buck to someone else.
Not to look for a variety of excuses. Do not say things can not do, and to say what can be done to salvage the situation. Then I see broken window effect, that is, when a tiny
After the error occurs, it will eventually result in chaos and collapse of the entire system, and cited in the book and the concept of entropy for the broken window effect, not on software projects in a small error or
Mistakes lightly, or else the software may eventually cause rot. I understand the software development environment is very important, if each person write the code are beautiful and easy to maintain,
So if you are a developer, you will be affected, the final development of the perfect completion of the project. We do team development catalyst, reasonable use sophisticated way
And the success of some of the key points you want to pass to the people, so better able to put good ideas into sound projects. Let me understand not just focus on their own side of things, we must continue
Observe what is happening around. I also understand that lets the user needs to become project quality criteria. And when the user needs more time to select the most basic and most
Development standards for important projects. This can be a good stop, it will not be destroyed because of excessive modification program. In addition, I also understand the need to constantly learn new technical knowledge,
But also to learn other knowledge with their technology-independent, learning to do as the financial investment, it is worth learning or find more helpful for their future knowledge. In addition, I
They should be more exchanges with people outside the industry, must pay attention to encounter problems solved in time, can be resolved through a variety of ways. I also learned to use a critical eye to look at
Questions, answers others have their own point of view, can not lose their thinking. Finally, I know the importance of communication, we have to study and exchange, you know what I mean
What, you want to know my audience, the opportunity to choose, choose the style to communicate, use and beautiful way to communicate with others, such as looking documents, etc., let the audience participate in the exchange, to
Listen to their ideas, to others and to make appropriate and timely response.
These are the first chapter of the book review I read The Pragmatic Programmer, I gain a lot, but also understand a lot.