The programmer should do every day. 1, sum up the completion of the day's task is the best way to write work logs, do what is done today, I met what the problem was recorded, and I'm going to look at it. 2, consider yourself The main work that tomorrow should be listed in the things you have to do tomorrow, and in accordance with priority, the second day should assign the highest efficiency to the most important work 3, consider the mistakes in our work, and think It is not tight that the next time, it is wrong, the most important thing is to repeat the same mistake, it is stupid 4, considering whether the quality and efficiency of the work completed on one day can be increased by 1%, 365 days you How many times you know if efficiency? (1 0.01) ^ 365 = 37 times 5, look at a useful news site or read a useful newspaper, understand the industry's dynamic closed door is not good, learn what others are doing, and bring a lot of revelation to yourself 6 Remember the name of a colleague and its characteristics do you know all the company's colleagues? Do you know them? 7. Clean your code today to complete the code, clear the intermediate debugging information, test code, according to the coding style, is there a good note? 8. Clean up your desktop when the day is on the day, keep the clean desktop to make you worked out, the programmer specially cleans the computer's desktop to clean the program 1, to your boss Once makes your boss know what you are doing, it is very important. Can be oral, written, email, see your boss's work mode 2, make a self-summary (informal) How do you express your performance within this week? Is this additive or deducted? 3. Develop a next week to list the things you want to do next week, just clear the priority 4, organize your folders, bookcases and computer files to clean the desktop, clean, computer folders, The email, all cleaned up the outdated garbage, communicate with a non-company friend, can attack jade 6, watch a magazine to find a professional magazine for yours, correct your or colleague a detail Is the incorrect practice "Detail decision success or failure"? I haven't seen it, I have to look at the programmake 1, at least with a colleague, eat or drink tea, not only to understand my work partner, I have to understand their lives 2, self-assessment, one relatively official assessment I will find this month's salary. 3. What is the performance of your colleague for your colleague? Who is worth learning, which people need help? 3. Develop a next month, determine the focus of the next month, summarize the quality improvement of your work quality improvement? 5. It is targeted to analyze a work indicator and draw a improved program. It can be for yourself, or to the company, you must have a deep analysis to come out. If you want to say something in front of the boss, do your business, work hard. 6. It is best to communicate with the boss. It is facing yourself. It looks at yourself. It is more important to understand the key programmer of the boss's current concern. 1, year-end summarize each company Do something, but do you really concurretal? 2, give yourself, give your family a promise to my wife, my son's New Year gift is there? Give yourself? 3, next year's work plan, think about your development goals next year, fight for promotion / salary, and do you come out? 4. Master a new technology is at least one. As a programmer, a new technique does not learn, it will be eliminated.
