程序员知识结构1（国外英文资料）.doc

程序员知识结构1（国外英文资料） This article is adapted to the reader: recent graduate students who have just entered the software company and are planning to develop in the software industry First, lets take a look at what happens when you enter a software company: You may often find that after writing a piece of code, the compiler is a bunch of errors (the reason: bad grammar) Dont worry, this is something that every programmer has to go through, and thats when you need to be more patient and careful. To carefully read every line of code and correct, this is very important, it can cultivate your ability to understand the code, so application will always read, dont wait until after the program is run to know the result of your application. How to avoid it: before writing code, be careful to learn the grammar of computer language, such as key points, fallible and easy to forget. Also write your own test code yourself, and try not to copy other peoples code samples. Even if copying, try not to copy each line exactly the same in the learning stage. The code sample writes a different example. For example, when youre learning about Java, youd better build a project to write all the code in this project, in order to learn from the analysis. You may often find that after youve written a code, you compile it, but youre running a lot of logical errors. (reason: understand the wrong or the wrong logic.) -- -- improve logical thinking and understanding Get a requirement and dont know where to start (dont know much about the system) Often for a small mistake, I dont know where to find it The things that are often made are the east but the west. Sometimes it is time for a special function module to be searched but not found. Do you sometimes ask for a project manager to call you east, and do you have no necessary west? (communication is not timely) Sometimes in order to finish a task ahead of time, working late into the night, but tomorrow is inefficient, its better not to work overtime (pay