September, I read the "practice of the Road programmers - from small work to the experts," this book, although only a small section of which read, made me gain a lot, gain a great deal.
From "Pragmatic Programmer's Road," the introductory part of this book can be seen, the book is a great work, the book consists of a series of independent parts, about the many entertaining anecdotes, thoughtful examples, and interesting analogies, rich in content, and the book also illustrates the many different aspects of best practices and major pitfalls of software development, whether a beginner or an experienced programmer who can benefit from . The book is exemplified many programmers think about this book, let me introduce them in recognizing the importance of this book for a programmer, it is worth every learning programming people to read, to learn, whether programming unskilled laborer or programming expert, this book can eventually become an excellent source of useful information. I understand that programming is an art, with the most simple words, the programming can be attributed to let the computer do what you want it to do, as a programmer, you both a listener and counselor from order theory both interpreter who is calling the shots, programming is hard work, to be pragmatic, we should learn from this fun programming, find ways.
The first chapter of the book is talking about time-sensitive philosophy. Time-sensitive method is not only a programmer, more responsibility. They are able to think beyond the immediate problem, always try to put the issue in a broader context, try to keep the bigger picture. Another key to their success is that they are responsible for everything they made. The first chapter of "our source code to let the cat to eat a" lively humor of programmers to write source code loss problems, then introduced us to the question of responsibility, pragmatic programmer responsible for his or her own career, and not afraid to admit ignorance and error. Even in the best projects, mistakes are inevitable, such things happen, we have to deal with them as occupation, which means that we have an honest quality, qualified as a programmer, we We can be proud of our ability, but for our shortcomings, our ignorance and our mistakes, we must be honest. It is responsible for the things we have to take the initiative to undertake. Then, the book describes the entropy of our software, as we introduce the influence entropy in software programming for us, the entropy is defined from a physical, it refers to the total amount of disorder in a system, when the software sprawl, programmers called "software rot" and then cited reason "broken windows" and "fire" and other stories, illustrating the code in a program, if a team write code very pretty neat, clean and elegant design, then you likely do not pay attention to it "dirty" because nobody wants to be the first person dirty things. Then the two told us the story of "Stone Soup," "warm boiled frog", "Stone Soup" tells the story of three soldiers cook a pot of delicious soup with stones, so that people feast on the story, from the beginning of stone soup, and then by people who each have a little food, and finally cook a pot of delicious meal. Everything is from scratch, no results are built up little by little, to do the project, too, it was a team, everyone is a little force play to their strengths, and finally combined, and this is a perfect project, everyone on the team is a winner. It can be seen, the team's cooperation is very important. Furthermore, "Wen boiled frog" tells of a frog in hot water, the frog will jump out, and cook slowly into the warm water, the frog will be cooked, the story tells us, do not like a frog Like, to pay attention to the big picture, to continuously observe what is happening around, instead of just doing your own thing. A good enough software code is not called clean enough, but can make the software to meet the needs of users, in order to be successful, so we should use to Households opportunity for users to participate in a trade-off, furthermore we should know when to stop, not because of too excessive modification and refinement and damage the integrity of the program. As a good programmer, we have to learn how to manage and run their own knowledge assets, set a goal to read more books, and other learning opportunities to seize, and then you learn to think critically and hear . However, as a qualifier, we have to learn to communicate, know what you want to say, know your audience, choose the timing, style, so friendly document, let the audience participate, those who do listen, and reply to others.
The above is what I feel from the first chapter of the book's proceeds, let me profitable.