GitHub R & D Management: time-based measurement of programmer's work

 

8 working days, many IT companies in China are definitely working systems. Does this system help developers to work efficiently? In addition, how does a flexible work system affect developers' work efficiency? Zach Holman, a well-known open-source hosting platform, wrote a series of articles to share his path to operation management. How GitHub works: Hours
Are bullshit is the first article. csdn compiled this article. The full text is as follows:

As the saying goes, time is money, and the faster the better. The more time, the better.

It's a lot of fun with programmers.

In many industrial enterprises, time is a major factor in determining production efficiency, but not for GitHub. In a startup company, you cannot spend more time on a problem to solve it thoroughly. Code is the direction of effort. You need to have the correct mindset to create high-quality code.

Think back to the last time you were impressed or angry. How efficient is your work? Think back to your recent truly efficient experience. Code is produced from the fingers. When you have the right way of thinking, efficient code programming on a day is better than a week's frustrated programming work.

We want employees to work in this status as much as possible. Limiting the time for employees to work in the office will affect their working status. If it is required that I have to arrive at the office before, it is difficult for me to maintain this efficiency, but for half of employees on GitHub, the morning may be the best time for them to work.

Allows employees to work more flexibly and creates an exciting working environment. In this environment, they can work longer and maintain efficient work efficiency.

One day's work

On GitHub, each person's daily schedule is different. Similarly, my daily experience is different. The following is a rough schedule:

1. Get up at around ten o'clock A.M;

2. Take a bus to work and have lunch at noon or one o'clock P.M;

3. Find a place to work at one o'clock P.M. and Work in the Office from six o'clock P.M.;

4. Go home and work or rest on the sofa at home until two o'clock in the morning. Sometimes I also go out for dinner with my colleagues.

Some colleagues may come to the office at seven o'clock A.M., and some may come at three o'clock P.M. Some colleagues think that working at home is more efficient. If employees do not like to work in the office, they do not need to come to the company every day (although in most cases, everyone will come to the company ).

Why are we so "loose" in one day? Two reasons: First, working in a loose environment allows us to work at our favorite time and place; second, we hope to create a work environment that maximizes the efficiency of our employees. Because everyone works efficiently at different times, we will not force anyone.

Restrictive work

Currently, GitHub has 35 employees and is still growing. This method brings good results. However, managers still like fixed working hours because they have the illusion that time is the standard for measuring the work of employees.

If you are hard to grasp the work time, you need to find other measures. Is their code well written? Have they handled all the bugs? Are they fully engaged in their work? Is higher flexibility at work motivated?

It is difficult to make a qualitative judgment on this, but these methods are more valuable than "doing this well within 10 hours of the working day. Because when you use time to measure work, their work will become more time to write less code.

Original article:How GitHub works: hours are bullshit

(Translation/csdn Chen qiuge)