Day work programmer vs Night work programmer, night work type wins

When I visited the website, I saw an old article titled "The Day Programmer vs. the night Programmer", which was written by Mitch Denny, because Mitch Denny served as CTO for a company, and the article has been issued to attract hot and Post. The article is translated by netizens, in order to let us see more clearly, some places to modify.

Years ago I believed that there were two kinds of programmers in the world, no matter what technology they used, I would call it:

1. Day Programmers Daytime working programmer

2. Night Programmers night-work programmer

Today, the most common part of the industry is daytime-working programmers, and you'll see them in a lot of inefficient companies/organizations that tolerate a certain amount. They have the following characteristics:

1. Usually in the lead, seldom as a leader;

2. Difficult to deal with complex situations;

3. It is difficult to imagine a solution;

4. Do not open development tools at home;

5. Usually not involved in the technology development community;

6. The programming is only as "a job";

If you're a night-time programmer, you might find it hard to understand why working-day programmers can get into the business because their motivation is very different from your motivation. The characteristics of night-working programmers are:

1. Usually play the lead role

2. Have a deep understanding of complex matters;

3. Can conceive the solution, and has the design related Sixth Sense;

4. The Alpha/ctp/beta version of the tool will be opened at home;

5. Participate in user groups and mailing lists;

6. Think of programming as an important part of life, like the air needed for life;

If you're a daytime working programmer, you see working programmers at night who think they won't enjoy life. When they get excited about some cool new tricks at work, you still scoff.

Last December, a blogger wrote an article: Why do programmers like to work late at night? "It is written in this way:

A very popular word is that programmers are the machines that turn coffee into code.

Sure enough, ask a programmer when it is most efficient, and it is likely that they will say mostly late at night. Some early, some late. Common: Get up at 4 o'clock in the morning and finish some work before the noisy day begins. Others like to sleep at 4 o'clock in the morning. The purpose of this approach is to avoid interference. But you can lock the door, why is the night so special?

Not only programmers, for many industry practitioners (writers, editors, etc.), in the dead of night, often is the most easy to find inspiration, efficiency is very high. And generally enter the state of work, mental state is very well, not sleepy, imperceptible to three or four points. Remember to read the news online, said the night 11 o'clock to 1 o'clock in the morning two hours of sleep the best effect. If you do not sleep for two hours, you will feel more awake during the day, and often still faint. Staying up late for the health of the body, the day before yesterday to forward an article has been explained, and needless to say, we often see a lot of young people in the micro-bo it or entrepreneurial premature death information. What do you do if you meet a project that has to work overtime all night? Sleep at 11 o'clock in the evening and get up and work after 1.

The above is the whole content of the article, although the small series has not been optimistic about the night work-type programmer, but the face of the article such a powerful example, I also do not say what. Finally, I would like to remind everyone to pay attention to health after work.

　　Pay attention to Huaqing vision, reply "dry" 400 yuan ebook, every day 5 o'clock in the afternoon 30, wonderful content to feed you.

Day work Programmer vs Night work programmer, Night work type wins