……盯着项目管理工具里的指标，就如同丢了钥匙却只在路灯底下找，仅仅因为那里的光线最亮。认识到在系统中保持冗余（slack）且不要过度优化的重要性同样关键，正如汤姆·狄马克在他那本神作《 slack：超越倦怠、瞎忙与完全效率神话》（Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency）中所阐述的那样。
…metrics from your project management tools is like looking for your lost keys under the streetlamp because that's where the light is brightest. It is also important to recognize the importance of keeping slack in a system and not over-optimizing it, as explained in Tom DeMarco's excellent book Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency.
…be profitable when one resource is unavailable, then have more resources. This is as true of hard drives and fire exits as it is of employees. Expanding on a point by brational, see Tom Demarco's book Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency. It makes the argument that if your goal is long-term profitability, you must have some excess capacity in human resources at all times.…
He didn't - IIRC - talk about "20% time" specifically, but Tom DeMarco wrote a whole book about the importance of "slack" time at work. One point he makes is that if everyone is too busy doing the routine stuff 100% of the time, then the firm can't adapt quickly, because nobody has time to learn anything new, do exploratory…
* Thinking Fast, Slow by Daniel Kahneman * Steve Jobs, by Walter Isaacson * Slack, by Tom DeMarco (also re-read Peopleware). Both of these books are fundamental to anyone developing software within an organization. * Delivering Happiness, by Tony Hsieh. It's not fantastic but it's…
…point of the article. It is definitively not about programming abilities, or speed of these abilities. Many authors have hit TFA's points from different angles. For example, Tom Demarco's excellent Slack[1] introduces uses of "efficiency" (what speed is the organization moving at?) versus "effectiveness" (is the organization moving in the right direction?). DeMarco uses these to illustrate that many…
……盯着项目管理工具里的指标，就如同丢了钥匙却只在路灯底下找，仅仅因为那里的光线最亮。认识到在系统中保持冗余（slack）且不要过度优化的重要性同样关键，正如汤姆·狄马克在他那本神作《 slack：超越倦怠、瞎忙与完全效率神话》（Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency）中所阐述的那样。
…metrics from your project management tools is like looking for your lost keys under the streetlamp because that's where the light is brightest. It is also important to recognize the importance of keeping slack in a system and not over-optimizing it, as explained in Tom DeMarco's excellent book Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency.
……如果想在某项资源不可用时依然盈利，那就准备更多的资源。这对硬盘和消防通道适用，对员工同样适用。展开讲讲 brational 的观点，可以参考汤姆·狄马克的书《 slack：超越倦怠、瞎忙与完全效率神话》。它提出这样一个论点：如果你的目标是长期盈利，就必须时刻在人力资源上保留一定的富余产能……
…be profitable when one resource is unavailable, then have more resources. This is as true of hard drives and fire exits as it is of employees. Expanding on a point by brational, see Tom Demarco's book Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency. It makes the argument that if your goal is long-term profitability, you must have some excess capacity in human resources at all times.…
如果我没记错的话，他并没有特指“20% 自由时间”，但汤姆·狄马克确实写了一整本书来强调工作中有“从容/冗余时间”（slack）的重要性。他提出的一个观点是，如果所有人 100% 的时间都在埋头干日常杂事，公司就无法快速适应变化，因为根本没人有时间去学新东西或者做探索性……
He didn't - IIRC - talk about "20% time" specifically, but Tom DeMarco wrote a whole book about the importance of "slack" time at work. One point he makes is that if everyone is too busy doing the routine stuff 100% of the time, then the firm can't adapt quickly, because nobody has time to learn anything new, do exploratory…
《Slack》也是一本极好的书：http://www.amazon.com/Slack-Getting-Burnout-Busywork-Efficie...
"Slack" is also a great read: http://www.amazon.com/Slack-Getting-Burnout-Busywork-Efficie...
* 丹尼尔·卡尼曼的《思考，快与慢》（Thinking Fast, Slow）* 沃尔特·艾萨克森的《史蒂夫·乔布斯传》（Steve Jobs）* 汤姆·狄马克的《Slack》（还有重读一遍《人件》Peopleware）。这两本书对于任何在组织里做软件开发的人来说都是必读经典。* 谢家华的《三双鞋》（Delivering Happiness）。不算神作但……
* Thinking Fast, Slow by Daniel Kahneman * Steve Jobs, by Walter Isaacson * Slack, by Tom DeMarco (also re-read Peopleware). Both of these books are fundamental to anyone developing software within an organization. * Delivering Happiness, by Tony Hsieh. It's not fantastic but it's…
……这篇文章的核心。它绝对不是关于编程能力，或者发挥这些能力的速度。很多作者都从不同角度切入过这篇原文（TFA）的论点。比如汤姆·狄马克那本极棒的《Slack》[1]，就引入了“效率”（efficiency，组织跑得多快？）与“效果”（effectiveness，组织跑的方向对不对？）的区别。狄马克用这些概念来说明，许多……
…point of the article. It is definitively not about programming abilities, or speed of these abilities. Many authors have hit TFA's points from different angles. For example, Tom Demarco's excellent Slack[1] introduces uses of "efficiency" (what speed is the organization moving at?) versus "effectiveness" (is the organization moving in the right direction?). DeMarco uses these to illustrate that many…