10 caveats of old programmers

1. Rubber Duck Debug method

Maybe everyone has had this experience when you're talking to someone and suddenly you have the answer and other ideas, because when you talk to someone, you get your brain to reorganize the problem, and in that case, you're talking about "rubber ducks." So each of us should actively become the other side of the "rubber duck", so that we can get good advice to each other.

2. Information feedback should be timely

If you write the code, you should immediately go to your discussion area to discuss, and your "rubber duck" to exchange, listen to their suggestions, because now correct can be compared to your finished product after the change to save the cost of more.

3. Thinking in a different way

When you can't think of the answer you want, you might as well leave your job, consider it in a different way and place, it's sometimes really effective, there are a lot of friends around to talk about this way, and sometimes when you go to the toilet or take a nap, you really can think of the answer you want, or not believe. In a word, a change of environment really helps you.

4. Benefits of automation

Many programmers think that automation can only save time, which is a complete misunderstanding. He is not just so, the biggest advantage of automation is that he can make your mind without obstacles, can move forward to the goal. Let's say that we often run complex queries and re-enter them every time, and of course, you don't really do it like that, everyone uses the Clipboard or other tools, and I think automation is more effective.

5. Use "Take doctrine"

We all want to write the perfect new code, with new abstractions. But when we design new code, the abstract concept becomes our obsession. When I have this kind of trouble, I'm not thinking about abstract concepts right away, but copying some of the code as prototypes first. So you can get started with new projects, and the effect is good, but to remember, do not only copy, but also to clean up the code, otherwise it will be difficult to clean up.

6. Proper movement is necessary

Because we often have to do in the computer for a long time, so sedentary so that we often backache. Because some want to have a good body will often exercise, otherwise nothing is wasted. At least three times a week more than 1 times is hard for everyone to stick to.

If you really like what I said difficult to insist, may wish to try the vertical table, he may be standing can sit down, so that you can easily solve the problem of sedentary at work.

7. Learn the previous article

Whenever I read a new article there is always some place to make people confused, in order to better read and understand the article, we'd better first look at this article Wencai good, so as to better help us understand the current article.

8. Record Notes

Some people can have confidence in their own memory, so the way to note this is very disdain, but I will take notes every day, so the problems encountered and how to solve these problems in detail, and so on, and so on these problems will soon be resolved, I bet, Even if you have a good memory there will be some things can not be remembered, so pick up paper and pen record.

9. Plan ahead

After a day of work I will put the next day's work schedule, so that the next day will not be too blind, the goal is very clear. This method for the second day of work really has a quality improvement and speed of acceleration.

10. Summary

All of the above content is not necessarily useful to everyone, but this is also a long time for individuals to engage in the development of a experience, I hope to help you.

10 caveats of old programmers