请问HN：我们是否将效率与“100%利用率”混淆了？
我最近和一位工程师进行了交谈，他在1981年使用Apple II优化了百得（Black & Decker）的装配线。他描述了他们如何以小数秒为单位测量原子级的手部动作（伸手、抓取、定位），以平衡装配线。但他提出了一个让我印象深刻的区别：
在那个时候，目标是流畅性（Flow），这本质上需要系统中留有一些余地。而今天，他认为现代管理的目标是利用率（Utilization），即消除每一个微秒的停机时间。
他的名言是：“我们删除了‘等待’，但我们忘记了等待是人类唯一可以喘息的时间。”
我感觉在软件工程中也看到了这种模式。我们将开发者的闲置时间视为需要通过JIRA工单消除的缺陷，而不是思考所需的必要余地。
问HN：对于那些在行业中工作超过20年的人，你们同意吗？
查看原文
I recently had a conversation with an engineer who optimized assembly lines at Black & Decker in 1981 using an Apple II.<p>He described how they measured atomic hand movements (reach, grasp, orient) in decimal seconds to balance the line. But he made a distinction that stuck with me:<p>Back then, the goal was Flow (smoothness), which inherently required some slack in the system. Today, he argued, the goal of modern management is Utilization (removing every micro-second of downtime).<p>His quote: "We deleted the 'waiting,' but we forgot that the waiting was the only time the human got to breathe."<p>I feel like I see this exact pattern in Software Engineering now. We treat Developer Idle Time as a defect to be eliminated by JIRA tickets, rather than the necessary slack required for thinking.<p>Ask HN: For those who have been in the industry for 20+ years, do you agree?