1. Write a small program, please draw the program process box; write a big program, please draw a segmentation program process block diagram;
2. The source code does not understand, try the flowchart or segmentation flow chart of the program, and combine the source code to engage in the role and meaning of each variable in the flowchart;
3. Before reading the source code, please compile the program first, look at the way the program is running, gets a sense of understanding;
4. Remember: Users interface and interface to separate some of the core algorithm and processing;
5. To know: The program flow graph is a lot of species;
6. Please pay attention to "More Exceptional C " and "Effective STL";
7. Learn to configure the integrated development environment and make full use of the convenience of integrated development environment;
8. Please learn the knowledge of CMM (capability maturity model);
9. Please see
10. Please go to www.gotw.ca to see the Guru of The Week section;
11. Learn to use the good things in Standard Template Library, master the model technology - in fact, STL already contains such things, you can save a lot of troubles that you have written basic data structures and algorithms;
12. When I first study, I must pay attention to debugging technology. I learned to analyze the procedures using Debug. Although the procedure at that time is very simple and simple - to develop a good habit of debugging;
13. Please pay attention to the integrity of the program - a small program, it should also have related borders to handle and error handling - I don't want to run your code for a long time, if you run your code, if the program is not The unexpected result is even mistaken, that is not a pleasant thing after all.
14. Compile the same program using different compilers, perform horizontal comparisons - this often helps to solve the problem related to the C standard and compiler;
15. Lazy people like to ask: Is the XX book good? How about YY book? - Don't ask, please judge yourself through the bookstore or library preview; the book that is suitable for others is not necessarily suitable for you; someone else's view is just a reference;
16. Lazy people like to call: Please help me write XX programs (ask YY)! - I hope you can politely ask questions about "design ideas for XX-type procedures" and then resolve themselves;
17. Lazy people like to complain;
18. Lazy people must not read less books;
19. The lazy person is not necessarily a few people who have added less.
20. Lazy people generally are also impetuous;
21. Two kinds of lazy divisions: a) Ideological; b) action;
22. Lazy people are divided into two: a) only people who don't learn; b) people who only learn and not practiced;
23. Impetuous people like to evaluate various languages: XX advanced, yy behind; XX "fast", yy "slow"; - Is YY really "slow", or your algorithm is too bad? (Suppose you have made a true test of a true sense);
24. Don't evaluate a language easily - this is often a thing that only the masters or experts in the field;
25. When you beginaria, please deliberately prepare some small procedures, see all kinds of information, such as the size of various types on a specific compiler, and their allocation in memory, etc. - When I was impressed, I sometimes helped to solve some procedures for solving some procedures that make people couldn't touch the mind; 26. When I start school, many books should be able to take a side attack, comprehensively advance;
27. Remember and pay attention: When you begin school, it is the easiest way to get lazy and impetuous;
28. When you ask questions to others, please prepare information and problem backgrounds related to the problem so that others can quickly "enter the status" - otherwise, even if they have the authority of experts face your problem, there will be one It is not ready to feel in the face of "flying to the disaster";
29. Please ask others to ask others to ask others, thus avoiding repeated questions - after all, a person must endure you asking you to ask him that the same may have a little childish problem is not easy - - To respect others;
30. Please remember: When others answer questions for you, you can often learn a lot; when you answer questions for others, you can learn more; - Please pay attention to the problem of others;
31. When discussing others, don't despise each other - otherwise, others often despise you; - Discussion, solution needs patience;
32. If you think a book is very good, please remember to write a letter of thanks, the translator;
33. Please record anything you are not satisfied in your book or think that there is a mistake;
34. Please don't do lazy people;
35. If you love C , please support C .
