Ask HN: 我们是否混淆了效率和“100% 利用率”？
7 分•作者: nickevante•23 天前
我最近和一位工程师聊了聊，他在 1981 年使用 Apple II 优化了 Black & Decker 的装配线。<p>他描述了他们如何以十进制秒为单位测量原子级的肢体动作（伸手、抓取、定位）来平衡生产线。但他做出了一种让我印象深刻的区分：<p>那时，目标是“流畅性”（顺畅），这本身就需要系统中存在一些松弛。他认为，如今，现代管理的目标是“利用率”（消除每一微秒的停机时间）。<p>他的原话是：“我们删除了‘等待’，但我们忘记了等待是人类唯一能喘息的时间。”<p>我觉得我现在在软件工程中看到了完全相同的模式。我们把开发者的空闲时间当作一个需要通过 JIRA 工单来消除的缺陷，而不是思考所必需的松弛。<p>向 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?