dependency-graph
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseGiven a batch of work items, map which block which. Look past the dependencies items declare outright — the ones that bite are implicit.
给定一批工作项，映射它们之间的阻塞关系。不要只看各项明确声明的依赖——真正影响大的是隐含依赖。
Blocking edges
阻塞边
Item B is blocked by item A when B's text says so, and also when
- B needs something A produces — code, infrastructure, or data,
- B and A touch overlapping files or modules — a collision, not an order; pick one to go first and treat the other as blocked by it, or
- B's requirements hinge on a decision or interface A will establish.
当项 B 的文本明确说明时，项 B 被项 A 阻塞；以下情况也构成阻塞：
- B 需要 A 产出的某些东西——代码、基础设施或数据，
- B 和 A 涉及重叠的文件或模块——这是冲突，不是顺序问题；选择一个先做，将另一个视为被它阻塞，或者
- B 的需求依赖于 A 将建立的决策或接口。
The frontier
前沿
The frontier is the set of still-open items with zero blockers — they can start now.
Recompute the frontier whenever an item completes.
Done when: every item is classified as frontier or blocked, and each blocked item names every item it waits on.
前沿是仍处于打开状态且没有任何阻塞者的项集合——这些项现在就可以开始。
每当一个项完成时，重新计算前沿。
完成标准：每个项都被分类为前沿或阻塞，并且每个被阻塞的项都列出了它所等待的每个项。