Suggested Ma Yundong (XACN) for primary programmers
Recalling that I have been more than three years. Now I remember that I found out that I didn't know how much bending. The programmer refers to the programmer who has just participated in the work. It is also a thing for Chinese software! (This is too too much, but it is better than some parsers to guide software development.) Still don't say these, let me enter the topic!
1. I have always thought that it is the most important thing. Now I know that simple is good.
The more skills used in writing code, the higher the level, the higher the level, and now I know the simplest to complete it is the best. Write procedures are not like writing novels, the more fluctuations, the more the fluctuations, the more people who can't stop. If you write a program, it is like writing a novel, and the person who reads your program is "this dead, why do you do this!"
2, the code written for realization, we have to stay
In the past, when I read the book, some code will be verified, or some issues encountered in the system development are verified, and it will be deleted when the verification is finished. This is not good. Although you have completed some features in the system, you can not remember too much in the future. You only go to a relatively large system to find this functional program you want, you will find that you are a stupid. If the previous verification case is not deleted, it will be easier to find it. And the subject is also more clear. In this regard, Yang Da brother on www.vckbase.com is the example of our study. When you ask questions, he always gives an implementation example code. If he is not usually done in advance and saves. Call him to find a big project. I don't think so quickly! (Ask Yang Big Brother a private issue, how much g is this in your hard disk?). So don't think you have verified it, you can delete it because you can't remember so much. I know that knowledge is getting more. Any person is impossible to completely remember. I don't know how everyone did it? I did this, write a good example code all classified storage. For example, VC is written, I created a "VC Program" directory. In addition to all example code written by the VC, there is an additional documentation. If "instructions .txt", record that directory is to verify what functional examples. In this way, when I encounter the function you want, you can clearly find the desired instance code as long as you open the "instructions .txt". Open the project As long as the Copy source code is to the system, the modification is changed.
3, prepare a notebook for yourself, a pen
Any advanced programmer is coming over by a primary step. However, there is a fast, some slow, and some will always be a primary. This is mainly the result of the summary of the records that are not recorded in some experience. The human brain is impossible to write a few gs. We will find information when we receive a project. If you record the useful thing you see in advance, you will record it in your notebook or computer. This is faster to find. Slowly as your notebook increases or the capacity of the hard disk increases, you step out of the primary programmer. The notebook I here is mainly used to record some simple questions. If you look at the comments inside www.vckbase.com, there will be some people asking something, but you don't have to use it now, I will write it down. When I use it next time, I can only find a notebook. Of course, the problem on the notebook is mainly small. Such as: "How to make the window in the foremost? How to traverse all controls in a window?" And so on. The answer is not too much. So I wrote it. In this way, when you use these things, I don't have to go to the Internet to help, find a note. It can improve the development speed.
4. Requirements for primary programmers when job hunting
The primary programmer is less than the job search. Actually, because you approve is just a primary, it is not too high. But one thing to remember, code must be standardized (naming specifications, annotation specifications, writing specifications, etc.). This is quite configured. Because the communication between programmers and programmers is mainly deserved. Don't tell your Map (most Yunnan people talk about Mandarin is not too standard, the people outside the outside is Map.) He speaks his bird language (we call the Cantonese to call the bird language, there is no other bad The meaning, but because Cantonese sounds like a bird singing. I feel very nice. So ...). This is inconvenient to communicate, and there is also a person's development habit you can see from its code. Generally speaking, it is difficult to change the habit. So I think the primary programmer should not throw the code specification when writing the program. This will develop bad habits, it is difficult to change! 5, do a humophic person
The ancients said: "Three people must have my teacher." Whether it is a primary, intermediate or advanced program. Do not understand. So homingly learning to raise yourself. I have to talk about Yang Lao, who I have to talk about www.vckbase.com again. People who often get www.vckbase.com must know Yang Da Ge. If you haven't got it, ask me who Yang Da Ge, he is a VC Encyclopedia, which is far away. (I have never seen his own, but he gave me a lot of help. I have a chance to visit him.) He not only knows more special, but people are very modest and more unconservative. As long as he knows, he will help. It is more such as a primary programmer.
6, do a non-conservative person
I have a point of view, I don't know if you agree. People who don't spend money will not make money. Haha ... the same is true for technology. If you keep technology, you will not have a bigger breakthrough in technology. Only public your technology, you will have more motivation to study new technologies and break through new technologies to improve yourself. Just spend money, only keeps making money to have money. Due to the company's reasons, public technology is not allowed, but I have to do at least to ask yourself to ask yourself. This will have more understandings when you explain this technology for your colleagues. At the same time improve the relationship between colleagues. Let yourself get better with your colleagues. This is especially important in the development group. Said so much, just I am off, for reference only.
