According to csdn's student channel, Mr. Xiao talked about how college students work on coding standards and discussed variable naming methods.
Blog: http://blog.csdn.net/java2000_net/archive/2009/04/24/4106670.aspx
Discuss original address: http://student.csdn.net/space.php? Uid = 39028 & Do = thread & id = 287
Some people agree and some people disagree. I can't help writing a little bit of fun.
Programming specifications are very important. In Microsoft and other large companies, it is very difficult to think amateur if they are caught in the collective code review.
It is very important for companies and individuals. The key is,CodeIt should be maintained in the future. Generally,ProgramIt may be difficult for a Member to read the code six months later. Many Chinese companies rely on some cool people. Like Chinese sports, singles projects have hope and the team is not very good (especially for men's projects ). If a company's code is its core value, you must be able to understand it. In fact, it takes much more time for me to read code (find bugs, optimize, refactor, update, and so on) later than to write code for the first time. Why not accumulate points for yourself and others?
Sometimes I write code first to write (pseudo code) annotations, first logically think about what to do, and pay attention to alignment of the major arc (another good habit ). This may have something to do with my thinking model (I am an analytical model, I like top down from big to small decomposition, and I like mind map ). In this way, if the big logic is well designed, the details will be refined. Avoid thinking about the details of variable names and types from the beginning, which affects my thinking and design. If the design is to be changed, less investment will be invested.
After the design is complete, check the correct code. then implement the pseudo code in the specific language, so that the comments will naturally be well written.
Especially for students, you have little experience, and you must learn more "professional" skills in details. If you don't want to gain a hand during the interview, the experts will not know if they are killed. (In fact, the lowest score in the interview is a crucial hidden rule ).
URL: http://vincentyang.cn/blogs/vincentyang/archive/2009/07/17/849.aspx