Program What members should do every day
1. Summarize the completion status of your daily task
The best way is to write work logs and record what you have done today and what problems you have encountered. In the future, there will be many benefits.
> Poor memory. Haha
2. Consider what you should do tomorrow.
List the tasks to be done tomorrow and sort them by priority. The next day, we should allocate the most efficient time to the most important tasks.
> Worklist. Plan is very important.
3. Consider the mistakes you make during your day's work and come up with a way to avoid making another mistake.
Error does not matter. The most important thing is not to make the same mistake repeatedly. It is silly.
> Always summary.
4. Check whether the quality and efficiency of your daily work can be improved.
One day only increases by 1%. How many times can you increase your efficiency in 365 days? (1 + 0.01) ^ 365 = 37 times
> Make a little progress every day. Constantly improving yourself is the key.
5. Read a useful news website or a useful newspaper to learn about the industry trends.
It is impossible to build a car behind closed doors. Understanding what others are doing can bring a lot of inspiration to you.
> You know what you know and what you know.
6. Remember the name and characteristics of a colleague.
Do you know all colleagues in the company? Do you know them?
> Interpersonal success is an important factor in career success.
7. Clear your ownCode
The Code completed today clears the debugging information and test code in the middle, sorts out the code according to the encoding style, and write all the comments?
> Learn from each other. Sort by category to facilitate reuse.
8. Clean up your desktop
By the end of the day, a clean and energetic desktop will not distract you from your work. programmers should especially clean up the desktop of your computer.
> Special attention is the key to success. Focus on firepower and do the most important thing at present. Other things-do it after completion.
What programmers should do every week
1. Report a job to your boss
It is important to let your boss know what you are doing. It can be verbal, written, or emailed, depending on how your boss works.
> Make sure you are in the correct direction. Don't waste your life. In the end, it's useless.
2. Make a self-Summary (informal)
How did you perform this week? Should I add or deduct points?
> Weekly summary. Changxiu Changwu.
3. Prepare the next week's plan
To list the things to be done next week, we need to clarify the priority.
>>> Plan again. The importance of planning is visible. This is a short-term plan that directs recent work.
4. Organize your own folders, bookcases, and computer files
Clean up the folder on the computer, emails received, and all junk files outside the desktop.
> Organization is the guarantee for effective use of time, and it is also easier to put into work.
5. Communicate with a non-company friend
The Stone of his mountains can attack the Jade
> Yes, but it is necessary to make useful exchanges without discussion. Others' time is also precious.
6. read a magazine
Find a suitable professional magazine
> Find a suitable weekly magazine.
7. Correct an incorrect practice in the details of yourself or your colleagues
Have you read "Details determine success or failure? I have never read it. I strongly recommend that you first check it out.
> Details. The world's best products will be fine. It is good to develop habits.
What programmers should do every month
1. At least have dinner or tea with a colleague
Not only do you know the work of your partners, but you also know their lives.
> Broaden your horizons and increase your experience.
2. Self-Assessment once
Do you have to pay the monthly salary for a relatively formal assessment?
> Self-evaluation (price ). Summary.
3. Evaluate your colleagues once
How are your colleagues doing? Who are worth learning and who need help?
> You must have an expert. Good at learning.
> This is the shot. Helping others.
3. prepare a plan for the next month and determine the work priorities for the next month.
> Medium-and short-term plans. Direction plan.
4. Summarize your work quality improvement status
How much has your quality improved?
> Monthly summary.
5. Conduct in-depth analysis on a work indicator and come up with an improvement plan.
Either for yourself or for the company, you must 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.
> Investment and depth.
6. Communicate with the boss once
It is best to communicate face-to-face, show yourself well, and listen to the boss's opinions with an open mind. More importantly, you need to understand the boss's current concerns.
>>> It is the direction. Do not get lost or go wrong.
What programmers do every year
1. Year-end summary
What every company will do, but have you really summarized yourself?
> Seriously (Comprehensive)-Summary.
2. Fulfill your promises to yourself and your family
Have you bought a new year gift for your wife and son? For yourself?
> Work is only part of your life, and there are many more important ones.
3. Work plan for the next year
Think about your development goals for next year, strive for a promotion/salary increase, job-hopping, or do it yourself?
> Planning.
4. master a new technology
At least one item. If a programmer fails to learn a new technology 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.
> Truly grasp. I thought it was "How to use it -- correct and efficient"
5. launch a new product
It can be a real product or a class library, as long as it is something you create, let others use it, and make a contribution to the world. Of course, if it is really valuable, you should also collect registration fees.
> Accumulate. Over time.
6. reunite with your parents
Always go home to see, always go home to see
> Do not forget the focus of your life because of your work.
This article from the csdn blog, reproduced please indicate the source: http://blog.csdn.net/liflag888/archive/2006/10/16/1336448.aspx