Code Encyclopedia read Note 02

Continue to read the Code encyclopedia This book, feeling is good thick good difficult to chew ah. It's just starting to read. The authors say that focusing on building activities can greatly increase the productivity of programmers. I think on a project, thinking and design is standing in the leading position, if you can not think clear, may at any time there may be stuck there, and once the inspiration comes, you will want to come up with the same ideas, we also do a small project, although very low, but at least a little experience. We always in the design of the time will be cornered, at a loss, so that every start is not the idea of starting a hand can only backlog in there, really do not know how to do. I think P28 's example of the food chain is more convincing, in a healthy ecological environment, the seagulls eat fresh salmon, salmon eat fresh herring, and herring eat fresh water bugs. This is a healthy food chain. If the environment is polluted, water bugs swim in the polluted waters, so the seagulls, the last ring in the food chain, eat not only the rubbish in the unhealthy salmon, but also the contaminants in the herring and water bugs. In software development, the architect eats the demand, the designer eats the architecture, the programmer, the software's last ring of the food chain, and digests the design. If it is contaminated at first, we should not expect the programmer to be happy. The entire software will be radioactive, the whole body is a flaw, absolutely lead to the programmer grumpy, nutritional disorders. In our small team, a person and a number of jobs, the damage is greater. So, the project starts with a decision on whether it will succeed.

And then we don't have to go to the book. Write demand analysis books or whatever, do the demand analysis even in the brain, verbal communication is done, there is such a process. Falling text is good, but it's not the point. The key is to do not do. Whether all the input of the system is defined in detail, including source, precision, range of values, frequency of occurrence. Do you define the full output of the system in detail, including the purpose, accuracy, range, frequency, and format? is the minimum value for machine memory and remaining disk space defined? Is the maintainability of the system defined in detail, including changes that adapt to specific functions, changes in the operating environment, and the ability to change interfaces with other software? The book is much more than I have listed here, well worth reading. It is important to set these, I think reasonable game development, there is a relatively stable planning scheme, and some completed the completion of the art resources. Most of the changes are left in the next version. Planning and fine Art will always work for the next version, and the program can be designed according to the relatively stable requirements. In doing so, even if the first version is not playable, throwing it away will also make the game a success. I'm confused now. What exactly is the project document written about? Some of the things listed here have solved some of my doubts. If you choose to represent a set of data using a sequential access list, you should explain why sequential access is better than random access. During construction, this information allows you to gain insight into the architect's ideas. In the maintenance phase, this insight is priceless. There is a more interesting example behind P58: Beth wants to be a family stew of her husband, Adbul. Adbul said, sprinkle the pepper and salt first, then go to the head to the tail, and finally put the lid on the pot to stew. Beth asked, "Why go head to tail?" "Abdul replied," I don't know, I've been doing this, and that's to ask my mom. He called home to ask, mother also said do not know, she has been doing so, this question to ask Grandma. Mother made a phone call to grandma, Grandma replied, "I don't know why you have to head to the end, I do this because my pot is too small to fit":D The architecture should describe the motivations for all major decisions.

Although the reading is very few but the feeling is that some authors want to give us something in the inside, I think the experience of predecessors let us walk better, I hope I am not only usual.

Code Encyclopedia read Note 02