Some suggestions for new graduates who want to be programmers

Over the past few months, I have continuously seen discussions on the job, future, and work ability of recent computer graduates on the website. I have many feelings and have interviewed many graduates, I have read hundreds of resumes, so I won't talk about the Adverbs of understanding, familiarity, and proficiency. The actual programming skills are limited, and the online chat and playing games are relatively high. These are all facts. However, how can we quickly integrate into the company's development work? Continuous learning and practice.
Recently, I have been continuously engaged in internships for new graduates in the company. Some of my abilities to accept problems are faster, some are slower, and I have different abilities to learn new knowledge, but sometimes I am quite impressed, reading is very hard, but the actual programming is always not ideal. Later, he chatted with a graduate. He said: He can't remember what he reads. Another way is to read VC books and take notes. He said that this will deepen his impression and remember that he will not know how to write code during programming in the future, it makes people feel like they want to take graduate students.
I don't know how people learn new knowledge. I personally think that the way they study after going to college is very different from the way they do after work. When they go to college, many things need to be remembered for the exam, after graduation, you will know where to find the materials, and there is no need to remember some details. Of course, it is good to remember the details, but do not be troubled by the details.
Reading program code is a good way of learning. For the same code, beginners may be concerned with the use of some system functions and the use of data types, the relationship and function of derivation and inheritance, and the effect of overloading. After having some programming experience, I do not pay special attention to the definition and use of functions, variables, and classes in the code. I pay more attention to the code design ideas and design ideas, the relationship between modules and interfaces between modules. The key is understanding. After understanding it, you will naturally remember it.
There are many classes and many functions in MFC, and there are many different data types than standard C ++. Do you need to remember them all? You only need to remember some basic common ones, such as cstring, cdialog, cdocument, cview, awinapp, cmdiframewnd, cbutton, cedit, clistbox, ccombobox, ctreectrl, and so on in VC, these classes must know what they are and what they are used for. For specific usage, see help, afxmessagebox, try catch, Trace, lpctstr, uint, DWORD, wparam, lparam, sendmessage and so on are also worth remembering. These are often used to write VC programs. There is no need to remember too much. The key is to learn to use msdn and focus on code design. It doesn't matter how a function is called or how to use the F1 key. No search can be found on csdn on msdn or on codeproject.
Don't keep writing code, take time on some technical websites, and find out where to find the relevant information. Maybe one day, you know where to find the relevant information, learn to use free resources on the Internet.
Do not always work overtime, do not smoke too much, programmers do not eat youth, unless you choose to eat youth meals. Bill Gates is older than us, but he is Microsoft's chief software designer. He is definitely not a 20-Year-Old Man engaged in bottom-layer windows design. The development of software in China cannot rely on youth meals.
Learning to communicate and collaborate with colleagues is the most basic quality for a good team member. A very important reason for the popularity of Java is that the Java language can be used as a platform, and programs written in Java can be run in windows, or in Linux or UNIX, java is a very good language. A good programmer does not need to master a cross-platform language. However, he must have a "cross-platform" ability. This is team spirit and cooperation consciousness, to any company, any project team, or any team, whether they are using Windows, Linux or UNIX, whether they are developing CS-structured programs or developing bsstructured programs, both hardware and software development are the most important and popular capabilities. I told our interns that if they close themselves and don't help each other and don't unite, they will first go out.
I often see online discussions about what language to learn, what language is the most promising, what language is easy to learn, and what language is highly paid. I personally think that for recent graduates, the product development of the company does not play a leading role, basically there is no right to choose a language, unless you leave the company, because the company's existing products or projects determine the language to use, or the main developer of the product determines the language to use, you only have to accept. But is there any relationship? What language should you use, and what language you use for the products you participate in? It is not particularly important to learn the specific language, the most important thing is to learn a good design idea in practice, think about problems in computer language, and learn the abstraction and overview of real problems, learn to use a computer model to describe things in the real world. After a while, you are very familiar with a language. Looking at other languages, I think they are all very similar. If else, for, while, =,>. <, stirng, class, try catch, and so on have many differences. It is very easy to learn a new language. Of course, in many cases, we will be exposed to several languages. My colleagues and I have been using VC. Recently, I used C # To write a program to implement transaction reservation. After three weeks, the program passed the test and is sold as a hot potato.
The above text is for personal understanding and for reference only.