"Programmer's practicing the Road: from work to the experts' study notes two
Recently, continue reading the "coolie to experts", quite sentiment.
communicate with,
First, you must know what they want to say, plan what you want to say content, clarify ideas, to ensure that their language can express their ideas.
Second, we must understand their audience, their interests, experience, experience, etc., as their reference point for how to express one's own ideas. Third, we should choose the right time to understand the audience of "priorities" such that demonstrated his respect for them, and make their views, ideas more easily accepted audience. Furthermore, it should, according to the different audiences of different options exchanges style, so the time to explain the audience to participate, those who do listen, respond to others ......
As the book said, "What you say and how you say are equally important.", Whether in life or in work and study we can not avoid to communicate with people, and therefore plan their exchanges, because, the more effective communication, you the more influential.
Then continued reading the second chapter: focus on pragmatic approach. Pragmatic first step is to avoid unnecessary duplication. The system of any piece of knowledge must have a single, unambiguous, authoritative representation. And to do it we need to DRY -Don't Repeat Yourself (Do not Repeat Yourself), in that case we have to know that repetition is how it happened:
1) imposed repeat
2) repeated unintentional
3) No resistance to repeated
4) Repeat between developers
The book also gives the solution:
1.1, a code indicating a variety of information in the document, the code only requires a lot of bad comments, which can not be trusted worse than no comment.
1.2 documentation and code consistent updates.
1.3 language problems, interface issues should be documented with a header file, with the user a documented code without knowing the actual details.
2.1 Where possible, you should always use attribute functions to read and write access to an object, a future that will make it easier to add functionality.
2.2 Use accessor functions closely related to the Uniform Access principle, the principle states: all services provided by the module should be through the use of a unified representation, the representation they can not leak through the store, or by calculating the implementation.
3.1 refuse lazy, resist the temptation, earth work
3.2 "haste makes waste"
4 Developers are encouraged to take the initiative to exchange with each other, set up forum to discuss common problems, so a team member as project data administrator, whose job it is to promote the exchange of knowledge.
The second is to make good use of "orthogonal" (not in express some independent or decoupling, if a change occurs two or more things, and does not affect other things, these things is orthogonal , in a well-designed system, the user interface and the database code is orthogonal) as the book said: quadrature be
1, increase productivity, to localized changes, the development time and testing time is reduced, but also promote reuse, the orthogonal components are combined, productivity is improved;
2, reduce risk, the problem is confined to this area;