Pragmatic Programmer book review Road (C)

Read the third book chapters, so I understand the stability of the program, the robustness of the most important, in order to accomplish this, programming is best to use the most secure way of programming, such as text editors, though time-consuming, but but the most secure. Some storage space in exchange for the robustness of the program I think it is worth it.

Do not cover up blemishes intent of the program, the courage to admit, because the program is dead do not lie, crash test crash when the project is better than good in commercial use.

Let the tool becomes extended both hands
in plain text power Keep knowledge in Plain Text. Preserving knowledge in plain text. The power of the text: but when; leverage (as every tool can work in plain text); easier to test; plain text is always a common communication standard.
Shell game Do not be limited to the GUI interface, return to text manipulation, and let Shell to be your friend. Use the Power of Command Shells. Shell is using the power of command. Cygwin, UWIN Unix Shell is a tool for Windows under implementation.
Powerful editing Use s Single Editor Well. Good use of one of the editors. Editor features: configurable, extensible, programmable; Emacs is a good editor, Vi is, also EditPlus.
Source control is far from amusement progressive change in the composition, but on a good memory. Can not remember the past are sentenced to repeat the past. Source control system (the SCCS) is a long-acting Undo function. We can develop on the trunk, it can also generate some entire branch to the customer. If the branch in good condition, you can test
into account the branch and the main branch of the merger. Always Use Source Code Control. Always use source control. No matter how, as long as you work on a computer that will use it. VSS, CVS, PCVS, SVN is a very good version control system, there is ClearCase.
Debugging debugging purposes: to solve the problem Fix the Problem, Not the Blame fix the problem rather than blame. Do not Bug the face of panic or think it is impossible, since the occurrence must actively confront it. How exposed Bug: 1 best you can and report Bug person interviews about, so you can collect more data; 2 synthetic tests do not exercise enough applications must be designed to test the boundary conditions are implemented in the real world to the user usage patterns. ;
Do not let Bug testing strategy too far away from you, otherwise they will not catch it land. 1. With the data visualization: Variable name = data value (data representation visually) 2 tracking: a diagnostic message to a small screen or printed on the document, such as what printf or the like System.out.println;... b. trail stack (stack trace). 3. Rubber Duck: at another person explain your code, they spoke Bug came out; 4 elimination process: first find their own problems to find the problem, find someone else's problem; before then submit Bug reports, you must first eliminate your code Bug caused surprise elements: happened, to recognize, and then try to solve it. Do not Assume it-Prove it. Do not assume, to prove. After do not say: "Oh, My god" up.
Text manipulation Learn a Text Mainpulation Language. Learning a text manipulation language. Use lists: database maintenance, property access, test data generation, writing a book, interfaces, document ...... generate
code generator Write Code that Writes Code can write code to write code. Passive code generator: run only once to produce the result 1. Create a new source file; 2 a conversion into words only carried out between; 3 generating lookup tables and other run-time is very expensive resource; the active code generator..: All forms to be used to take a particular way of expressing knowledge every time you need a result, it will not convert your application needs, it means format conversion. ---------------- Disclaimer: This article is the original article CSDN bloggers "interhui", and follow CC 4.0 BY-SA copyright agreement, reproduced, please attach the original source link and this statement. . Original link: https: //blog.csdn.net/interhui/article/details/921421

Guess you like

Origin www.cnblogs.com/haheihei/p/11760760.html