An interview with programmers should not have eight errors

An interview with programmers should not have eight errors

1. do not prepare questions You must spend more time remembering your past experiences, including the projects you participate in, the various difficulties you encounter, and how to solve these problems. Your answers will affect the interviewer's impression on your technical skills, so you must review and organize your past project experiences. 2. relying on the answers recited in advance It is a very bad method to try to recite some answers in advance and then use them in an interview. First, there is very little probability that you will be able to answer your answers. second, such preparation will spend a lot of time and energy without actually improving your abilities. Remember, the better and more real you are at the scene, the higher the value you have. 3. Lack of interview simulation This is obviously because you have to prepare and simulate many things before doing so to prevent unexpected situations. The same is true for a Programmer Interview. if you are preparing a programmer interview, you should find some programmers you can prepare with you. you can simulate the interview scenario and ask each other questions. 4. the process of thinking is not presented. If you do not speak for a long time when answering a question, it will make you understand that you cannot answer this question. If you do not provide a thought process, the interviewer will not be able to understand your thoughts. However, if you keep talking with the interviewer, he will understand your thoughts and view your thinking process. this is very important. In addition, when your thinking is biased, the interviewer can guide you back to the correct solution. 5. writing code is inseparable from the editor. If you want to attend a technical interview, the interviewer usually asks you to write code on the whiteboard/white paper instead of on the computer. Therefore, you cannot rely too much on the code editor, because it will help you supplement the code and display your syntax errors. Take out the pen and paper and write down your code. when you are satisfied with the program you write on paper, input it into the computer and let the compiler verify whether it is correct or not. 6. failed to develop good programming habits Don't think you have done a good job because you only write a program that can be executed. You should also pay attention to the repeated code in the program, chaotic data structures, excessive spaces, and so on. Like in actual development, it is necessary to design a more logical data structure, a better framework, and a more clean and easy-to-read code. 7. no tests After writing your program, take some time to check your code to ensure that there are no bugs. If you are using pen and paper to practice, you need to write the program into the editor and let the compiler help you check. 8. always panic Do not worry when solving the problem, otherwise it will only lead to more errors, it seems very crude. You need to do things in a rational and accurate manner. you often look back at your code and correct them if there are any errors. In this way, the project completion time will be shorter, and there will be fewer errors. Get free LAMP Brothers original PHP video tutorial CD/the elaborate PHP Essentials edition, details consulting official website Customer Service: http://www.lampbrother.net