What a qualified programmer should do every month

What a qualified programmer should do every day
1. The best way to summarize the completion of your daily task is to write a work log, record what you have done today and what problems you have encountered. In the future, there will be many benefits.
2. Consider the main work that you should do tomorrow to list the things to be done tomorrow and sort them by priority. The next day, we should allocate the most efficient time to the most important work.
3. Consider the mistakes you make during your day's work and think about how to avoid the next mistake. The most important thing is not to make the same mistake repeatedly. It is silly.
4. Do you know whether the quality and efficiency of your daily work can be improved by only 1% a day or 365 times your efficiency? (1 + 0.01) ^ 365 = 37 times
5. Reading a useful news website or reading a useful newspaper, learning about the industry's dynamic closed doors, and learning about what others are doing can bring a lot of inspiration to themselves.
6. Remember the name and characteristics of a colleague. Do you know all colleagues in the company? Do you know them?
7. Clean up the Code completed by your code today, clear the debugging information and test code in the middle, sort out the code according to the encoding style, and write all the comments?
8. Clean up your desktop on the same day. Keep a clean and energetic desktop so that you will not be distracted at work. programmers should especially clean up the desktop of your computer.
What programmers should do every week
1. Report a job to your boss to let your boss know what you are doing. This is very important. It can be verbal, written, or emailed, depending on how your boss works.
2. Perform a self-Summary (informal). How did you perform this week? Should I add or deduct points?
3. prepare a plan for the next week to list the things to be done for the next week. The priorities should also be clearly defined.
4. Tidy up your folders, bookcases, and computer files, and clean up the folders on your computer, emails, and all the obsolete junk files off the desktop.
5. Communicate with a non-company friend about the rock to attack the Jade
6. read a magazine and find a suitable professional magazine.
7. Have you seen the "detail determines success or failure" incorrect practice in one of your own or colleagues' details? I have never read it. I strongly recommend that you first check it out.
What programmers should do every month
1. having at least dinner or tea with a colleague not only understands the work of his work partner, but also their life
2. Do you have to pay the monthly salary for a relatively formal self-assessment? 3. How is your colleague performing once? Who are worth learning and who need help?
3. prepare a plan for the next month and determine the work priorities for the next month.
4. Summarize the quality improvement of your work. How much has your quality improved?
5. Conduct in-depth analysis on a work indicator in a targeted manner and come up with a solution for improvement either for yourself or for the company, be sure to analyze it in depth and come up with your own point of view. If you want to talk in front of your boss, you have to do your work well.
6. It is best to have a face-to-face communication with the boss, show yourself well, listen to the boss's opinions with an empty mind, and more importantly, understand the boss's current concerns.
What programmers do every year
1. Summarize what every company will do at the end of the year, but have you really summarized yourself?
2. Have you bought a new year gift for your wife and son, as promised to you and your family? For yourself?
3. Next year's work plan should I think about my development goals for next year and strive for a promotion/salary increase, job-hopping, or do it by myself?
4. Mastering a new technology is at least one. As a programmer, if a new technology cannot be learned in a year, it will be eliminated. Understanding is not just about reading this book. To really understand the application, you 'd better write a tutorial and post it to your blog.
5. launching a new product can be a real product or a class library, as long as it is something you create, allowing others to use it and contribute to the world. Of course, if it is really valuable, you should also collect registration fees.