Reprinted, although it is not very suitable for me, it is still very reasonable!
The programmer should do every day. 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 date on the day, keep the clean and dry desktop can make you worry about it, the programmer specially cleans the computer's desktop clean
The programmer should do every week. 1. Report your boss once makes your boss know what you are doing, this 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"? Didn't read strong suggestion first
Programmers should do things every month 1, at least with a colleague or drink tea, don't just understand their work partners, but also understand their lives 2, self-assessment is relatively officially assessing yourself, you can afford this month Wait? 3. What is the performance of your colleague for your colleague? Who is worth learning, which people need help? 4. Develop a next month, determine the focus of the next month, summarize the quality improvement of our own quality improvement? 6. Totally analyze a work indicator to analyze and draw a improved program can be to himself, or to the company, it must be in depth, it will take out its own point of view. If you want to say something in front of the boss, do your business, work hard. 7. It is best to communicate with the boss. It is facing yourself. It looks at yourself. It is more important to understand the key points of the boss.
