林纳斯·托瓦兹的判断框架Linus Torvalds Judgment Framework

本课解决什么问题What this lesson solves

如果前四课解决的是“看什么”，这节课解决的是“怎么判断”。林纳斯·托瓦兹 的强大之处，不在于他总有答案，而在于他有一套稳定的排序顺序。

His judgment is unapologetically empirical: show the code, inspect the architecture, and let the implementation settle the argument. This lesson is where the course shifts from 'what matters' to 'in what order should it be examined.'

林纳斯·托瓦兹的四步判断框架。第一步：问题的底层约束是什么？。第二步：现有方案里哪部分只是历史包袱？。第三步：如果把 开源 作为核心变量，现在最容易被忽视的约束是什么？。第四步：围绕 工程审美 应该做减法还是加法？。这个框架可以在任何复杂决策中反复使用。

This is the lesson where the thinker becomes operational. If the order is wrong, the later action layer will also be wrong.

判断清单Judgment checklist

• 任何复杂判断先回到问题定义，而不是直接讨论方案优劣。The best framework reduces noise before it produces answers.
• 如果争论越来越大，通常不是意见不同，而是每个人盯的主变量不同。When teams disagree loudly, they are often tracking different primary variables.
• 林纳斯·托瓦兹 的框架擅长做减法，先砍掉不关键的动作，再谈放大关键投入。A strong judgment order survives low information and high pressure.
• 真正的判断框架应该能在低信息和高压力场景里重复使用。Do not let action outrun problem definition.

常见误区Common misreads

• 以为判断框架只是写在纸上的流程，实际没有配套信息筛选规则。Treating a framework as presentation theater rather than a real filter on attention.
• 一上来讨论解决方案，跳过了问题定义和约束识别。Jumping to solutions before naming the governing constraint.
• 把判断框架当成开会语言，没有落实到个人决策节奏。Using the framework in meetings but not in private decision-making.

课后动作Next actions

1. 拿你正在处理的一件复杂问题，按“问题定义 → 约束 → 动作”重写一遍。Rewrite one current problem as sequence: definition, constraint, action.
2. 把当前讨论中最吵的一项意见，翻译成它究竟更偏向 开源、工程审美 还是 直接反馈。Name which of open source, engineering aesthetics, or direct feedback is carrying most of the weight in your current debate.
3. 给自己设一个规则：以后先写出判断顺序，再允许自己开会讨论方案。Set a rule for yourself: write the judgment order before you allow solution discussion.

研讨题Seminar prompts

• 林纳斯·托瓦兹 的判断顺序里，哪一步最容易在现实工作中被跳过？Which step in Linus Torvalds's judgment order is most likely to be skipped in real work?
• 如果团队已经在讨论方案，而还没定义问题，你会如何把顺序拉回来？If the team is already debating solutions before defining the problem, how would you pull the sequence back into order?
• 问题的底层约束是什么？ 这句追问，在判断框架里究竟起过滤器作用，还是定方向作用？In the framework, does the opening question act more as a filter or as a directional anchor: Does the code work, does the architecture stay clean, and is the feedback loop honest enough to keep improving it?