Dream Break Code reading notes (5-7)

The fifth chapter-- bundle of geek and dog

How much code to measure a programmer's good or bad is the most idiotic way, a wonderful code is perhaps just a small piece of innovation, and that practice will only let more and more people knocking out more and more messy code. We can use a part of the time to find a concise approach to the path, ax, but we can't magnify this time too much. Like I was to cook and go to the supermarket to buy vinegar, but see the next clothes, stroll a half-day shopping malls, forget the ability is to buy vinegar.

The sixth chapter-- Complete the design plan

By reading this chapter, I realized the importance of backup to the program. Maybe we can trust ourselves enough, but we also have to set aside appropriate revocation plans for all the results. In the design of the program, we are always dreaming to complete a large development project, but the personal dream may always not stand on their own practical basis to extend the things, but not to say that can not try a large project, for this chapter of reading, I understand, from a novice point of view, We still should start from the foundation, do not embarrass themselves, down-to-earth, a small project to do excellent, and then go to the higher sky fly.

The seventh chapter--The details attempt

Persistence is a kind of concept, perhaps for many programmers to experience more profound, in this chapter I read a very fond words: Some programmers wandering in the dark clouds, the Buddha himself corrected every flaw in their hearts left a scar, and others, depending on the writing code as the only pleasure. The teacher told us that the program is an optimist, because for some of the big mistakes in front of their own time, in addition to their own comfort and optimism, we really have nothing. But I think it is this kind of optimism and perseverance is the greatest encouragement to me. I also hope this insistence can be rewarded as the book says.

Dream Break Code reading notes (5-7)