The second chapter is a pragmatic way,
In the first two sections about the closely related hazards and repetitive orthogonal to remind us not to repeat the entire knowledge of the system, not to any one of knowledge spread across multiple system components;
And reliable software development and make our development easier to understand and the only way to preserve is to follow the principle of what we call: the system must have knowledge of every single, unambiguous, authoritative representation.
No patience repetition
is an easy detection and treatment of repetitive form, should be trained in advance to avoid future pain;
Repeat among developers
, the best way to deal with this problem is to encourage developers to actively communicate with each other, you will not want to read other people's source code, which is not the spy, but as they learn;
Orthogonal system
is to eliminate the influence between things, can improve productivity, reduce risk; a project team effectiveness is that everyone knows what they do change, the opposite is the efficiency becomes low, which is a orthogonality problem, the team will become more efficient orthogonal;
Code:
make your own code to maintain decoupling, avoid using global data, to avoid a similar function, repeat code is a symptom of structural problems
Application of the orthogonality principle, reduce interdependence between the various components of the system. Development of the system will become more flexible, easier to understand and easier to debug, test, and maintain.
When the flexibility we write code to maintain the code, reversibility;
Tracer Code allows the user to see what can work as soon as possible, the developer build a structure something in which they can work, with an integrated platform with an integrated platform that can be used with the presentation, feel progress of the work;
Write code to be pragmatic, efficient, good to estimate the running time code;