0403 understanding of the fourth chapter of "Software Engineering"

First, code specification
1. Code style Specification: concise and easy to read without ambiguity, including meaningful naming and adding annotations
2. Code Design specifications
(1) function to do only one thing, and to do well
(2) Error handling. Verify the correctness of the parameters, use assertions, use Public,protected,private to explain the members, not necessarily using virtual functions and type inheritance
3. Code review

Two, pair programming benefits

1. In the development level can provide better design quality and code quality, the two partners to solve problems more powerful;

2. For the developers themselves, the pair of work can bring more confidence, high-quality output can bring more satisfaction;

3. At the level of enterprise management, pairs can communicate more effectively, learn from each other and communicate experiences, share knowledge, and better respond to people's mobility

Three, the pair of cooperation skills: to give feedback correctly
Like the onion, there are many levels, when the problem arises how to feedback levels?
Outermost: Feedback on behavior and consequences
Middle tier: feedback on habits and motivations
The inner layer: feedback on nature and intrinsic properties
Summary: 1. It is best to respond to actions and consequences when feedback is not involved in the middle tier and the inner layers of feedback. When the attack goes deep into the core, the attacking party is unable to respond, and it can be imagined that the depths of the conflict will have a less beautiful ending.
2. Good feedback should be the same as the sandwich, the first to pave the way, so that the other side feel in a friendly communication environment. Put forward the constructive comments, and finally affirm the commendable points, encourage each other

0403 understanding of the fourth chapter of "Software Engineering"