工作时间长短没什么鸟事 -- 来自Github的大神

 

Frederick Winslow Taylor wrote the seminal analysis of management and efficiency in 1911 with The Principles of Scientific Management. He took the first scientific approach towards maximizing efficiency in manufacturing jobs. Time is money. Faster is better. More hours are better.

有位叫Frederick Winslow Taylor的兄台，1911年写了一堆关于管理和效率的专题性分析，这堆文字顺理成章成了本叫《科学管理的根本法则》。他也是第一位科学的去研究如何最大化制造业工作中的效率。他所提到以下的几条法则，也就成为了以后的金科玉律：时间就是金钱，更快更好，工作时间越长越好。

 

Hours are bullshit

Hours are great ways to determine productivity in many industries, but not ours. Working in a startup is a much different experience than working in a factory. You can’t throw more time at a problem and expect it to get solved. Code is a creative endeavor. You need to be in the right mindset to create high-quality code.

Think back to the last time you were depressed or angry. How productive were you? Now think back to the last time you were truly productive. Code flying from your fingertips. Not just the sheer quantity- the sheer quality of that code. When you’re in the right mindset, your best day of coding can trump weeks of frustrated keyboard-tapping.

We want employees to be in the zone as often as possible. Mandating specific times they need to be in the office hurts the chances of that. Forcing me in the office at 9am will never, ever get me in the zone, but half of GitHub may very well work best in the morning.

By allowing for a more flexible work schedule, you create an atmosphere where employees can be excited about their work. Ultimately it should lead to more hours of work, with those hours being even more productive. Working weekends blur into working nights into working weekdays, since none of the work feels like work.

擦，工作时长是牛粪啊

很多产业都认为工作时长是一个判断产量的一个重要指标，我们才不这样认为呢。在一个初创型的科技企业跟那些工厂是不一样的，嗯，不屑跟他们一样。想想，出现一个技术难题，你砸了很多时间，就能解决吗？写码是一个创造性的成果。你需要的灵光的脑袋瓜才能写出好的代码。

想想你上一次的沮丧和发火的时候，你有多高产先？嗯，也顺便想想你最上次自认为是最高产的时候吧。你可能写代码总是噼噼啪啪的很爽。不过，写码是看质量不是看数量的，对不？你头脑好使的时候，美美地写一天代码比几个礼拜苦逼的敲键盘更有成就感，更有收获吧？

我们都希望员工有一个好的状态，天天好心情，好好写代码，不过那种死规矩的朝九晚六让他们待在位置上，反而员工不会有一个好状态写码。拿我来说吧，让我9点就回到办公室工作，无论如何也进入不了状态，不过有一半的Github人在清晨的时候工作状态特别好。

让我们的员工更灵活的工作，让他们把握工作的节奏，这种氛围让我们的雇员对他们的工作感到激情，yeah！热爱工作最终也让他们愿意更长时间工作，而工作时间也更高效，神奇吧! 周末工作也好，晚上工作也好，白天工作也好，没啥鸟不同了，工作已经不太像是在干活了，就跟你爱在周末里傻不拉唧看肥皂剧一般。

 

A day

Everyone at GitHub is different. I don’t really have an “average” day, but this is a close approximation:

• Wake up around 10am, check Campfire logs, clear overnight support tickets

• Bus into work and grab lunch around noon or 1

• Work from 1pm to somewhere around 6-9pm at the office

• Go home and work/relax from my couch until 2am, or:

• Go out and drink with coworkers (more on this later)

We have a contingent of (insane) people who come into work around 7am, we have some who come in at 3pm. We have some who are more productive at home. You don’t have to come into the office every day if you don’t feel like it (although most of the time everyone comes in).

Why is our day so “loose”? Because 1) working in chat rooms lets us work when and where we want, and 2) we want to create an environment where people are most productive. There’s no one work day that fits everyone’s productive hours, so we don’t enforce one.

一天是怎么过？

Github的人什么鸟样都有，你爱咋样咋样。你如果问我，我的每一天一般是怎样过的，我回答不了你哦，亲，不过大大概概就这样吧：

早上10点爬起来，看看Campfire 的日志，把一些过夜的ticket干掉，帮他们擦擦屁股

坐大巴去公司，猴急的把午餐吃完，12点，1点的样子

我开始干活了，从1点干到6点到9点这个时间段，当然是在公司

回家鸟，在我那舒服的大沙发上工作一下，放松一下，弄到凌晨2点左右，当然

有时我也想出去小酌一杯，跟我们公司那班鸟人扯一扯（待会再详细说说，擦，不是这篇文章交代）

我们单位啊，也有一帮傻不拉唧的鸟人7点多就来上班了，早起的鸟儿有虫吃撒。有些人下午3点才来，下午茶刚吃完。有些鸟人在家干活更愉快。你不想来公司上班，那就不必来了，没事（不过基本上他们都过来….）

我们的工作时间为什么这么松松散散呢？第一，我们的办公室让员工爱啥时候干活，爱在哪干活都行；第二，我们要创造一个环境让他们更高效高产。每个人都不一样，朝九晚六，朝八晚五都不可能适合每一个人，所以，我们不会强调一个固定的工作时间。

 

Enforcement

We’re currently at 35 employees and growing, and this approach still works great. But managers love to assign hours for a reason: it gives them the illusion that hours can measure performance.

If you don’t go hard on hours, you do have to look at different metrics. How good is their code? Are they fixing bugs? Are they involved in work, or is the greater flexibility not motivating them?

It’s difficult to make these qualitative judgements, but they’re still going to be more valuable than “did this guy put in his ten hours of work today”. Because as soon as you make it about hours, their job becomes less about code and more about hours.

强调的是….

现在团队已经35个人了，鸟人还会更多，保持这样的工作氛围还很给力啊。但是那些项目经理老爱给人分配工作时间，基于一个傻b的原因，他们幻想用工作时间去衡量工作表现。

如果我们不那么纠结于用工作时长去评估一个员工，那就要找换别的判断性标准鸟，代码写得好不好啊，修正了多少bugs啊，是不是真心认真工作啊，或者，这种灵活的工作方式会不会给他们的工作带来一些正能量啊？

顶，其实很难有一个量化的标准，对吧？不过即使无法作出所谓科学评估，还是比用旧一套标准“某男是不是在工作日里面的10小时工作时间都在看似很卖力干活”有价值的多啊。对于管理者，一旦你更看重工作时间，员工们也就更多去关心工作时间而不是代码了。