Code of Conduct for programmers

· Do not be confused by words such as VC, BCB, BC, MC, and TC-they are all integrated development environments, and what we want to learn is actually the same language;
· Do not let go of any seemingly simple small programming problem-they are often not that simple, or can draw out a lot of knowledge points;
· Visual C ++ is used, which does not mean that you can use C ++. Therefore, Visual C ++ books cannot be used to learn the C ++ language;
· It is not difficult to learn classes. templates, STL, and generic programming are also not difficult. What is difficult is to stick to the practice for a long time and spare no effort to read a group of books;
· If it's not a genius, you don't want to play games if you want to learn programming-you thought you did it, in fact, your C ++ level has not become higher together with your customs clearance capabilities-in fact, you can always remember that C ++ learning is for game preparation;
· It is better to keep outdated technologies in mind when talking about fashionable technologies;
· Read the books you can understand carefully. Read the books you can't understand;
· Don't expect that you can remember and master what you want to do when you read the first book-read the second and third times. [read the book for a hundred times, but do it for yourself]
· Do not stay on the cradle of the integrated development environment, learn to control the integrated development environment, and learn to process programs using the command line method;
· Discuss meaningful C ++ knowledge points with others, rather than quarreling XX rows or which is better for YY and ZZ;
· Read "program design practices" and strictly follow the requirements;
· Do not think that C and C ++ have the same syntax and keyword, so they have the same meaning and function;
· The secret to learning programming is: programming, programming, and re-programming;
· Remember: Object-oriented technology is not only proprietary to C ++;
· Please input the program examples in the book to your computer for practice, even if the supporting CD contains the source code;
· Expand the meaningful examples seen in the book;
· Pay attention to the Exception Handling Technology in C ++ and apply it to your own programs;
· Review programs you have previously written and try to rewrite them to apply new knowledge you have learned;
· Do not miss any exercise questions in the book-please finish all the exercises and record the solution ideas;
· The integrated development environment of C ++ and C ++ should be learned and mastered at the same time;
· Let the various platforms and development environments of the C ++ language go into fierce competition. We should focus on learning the C ++ language itself;
· Do not stop immediately when you write half of the C ++ program but find that your method is poor; please complete the remaining parts roughly as soon as possible to ensure the integrity of the design, and then analyze your own errors and re-design and write;
· Don't worry, it is really not easy to design C ++ classes; the class and the class design level in your program are improved and developed in constant programming practices;
· Every time I learned a C ++ difficulty, I tried to explain this knowledge point to someone else and let him understand it-you can clearly explain that you really understand it. [Teaching and Learning]