Advice on C # Learning

1. Take C # as a new language learning (it has nothing to do with C! True .);

2. Read professional books. Do not read them because they are difficult and we are beginners;

3. 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 a language;

4. Don't let go of any seemingly simple small programming problem-they are often not that simple, or they can draw a lot of knowledge points;

5. It is not difficult to learn classes. templates, STL, and generic programming are also not so difficult. What is difficult is to stick to the practice for a long time and spare no effort to read a group of books;

6. If you are not a genius, you don't want to play games if you want to learn programming. You think you have done it. In fact, your C # level has not increased with your customs clearance capability.

7. impetuous people may easily say: XX language is not good, so you should learn YY; -- you cannot do it yourself !?

8. impetuous people may easily ask: What should I learn? -- don't ask, it's right to learn;

9. It is easy for impetuous people to ask: do XX have money? -- We suggest you rob a bank;

10. impetuous people may say: I want a Chinese version! I cannot use English! -- No? Learn!

11. impetuous people may easily ask: XX and YY, Which is better? -- tell you, good.-As long as you learn;

12. impetuous people can be divided into two types: a) people who only wait and do not learn; B) people who only learn but do not stick to it;

13. It is better to keep outdated technologies in mind when talking about fashionable technologies;

14. C # not only supports object-orientedProgramDesign language;

15. One of the best ways to learn programming is to readSource code;

16. Never think that the books in your hands are enough at any time;

17. read carefully the books you can understand. Read the books you can't understand;

18. Don't expect to read the first book to remember and master anything-please read the second and third times;

19. 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;

20. Discuss meaningful C # knowledge points with others, rather than quarreling XX lines or which is better for YY and ZZ;

21. Do not think that C and C # have the same syntax and keyword, so they have the same meaning and function;

22. C # is by no means an "extension" of C. If C # is called the Z language at the beginning, you will not associate C with the Z language so closely;

23. Do not think that it is a problem if you have learned XX language and then changed C #-You just learned a brand new language;

24. The secret to learning programming is: programming, programming, and re-programming;

25. Remember: Object-oriented technology is not only proprietary to C;

26. Please input the program example in the book to your computer for practice, even if the source code in the supporting CDCode;

27. Expand the meaningful examples seen in the book;

28. Pay attention to the Exception Handling Technology in C # and apply it to your own programs;

29. I often review my previous programs and try to rewrite them to apply the new knowledge I have learned;

30. Do not miss any exercise questions in the book-please finish all the exercises and record the solution ideas;

31. The integrated development environment of C # And C # should be learned and mastered at the same time;

32. Since learning C # is decided, please keep learning, because the purpose of learning programming language is to master programming technology, while programming technology is cross-language;

33. when you write half of the C # program but find that the method you use is poor, do not stop it immediately. Complete the remaining parts as soon as possible to ensure the integrity of the design, analyze your errors and redesign and write them.

34. Don't worry, it is really not easy to design C # class; the class in your program and the design level of your class are improved and developed in constant programming practices;

35. never follow the rules you are not proficient in because the program is "very small"-Good habits are developed rather than remembered at once;

36. Every time I learned a C # difficulty, I tried to explain this knowledge point to someone else and let him understand it. It was just clear that you really understood it;

37. Record the knowledge points that you ignore or do not understand when communicating with others;

38. Please constantly put forward higher requirements for your own programs, even if your program version will change to version 100.xx;

39. save all the programs you have written-that is one of your best accumulation;

40. Do not be impetuous people;

41. Please love C #!