很长一段时间里，构建一个功能意味着打开一个文件，编辑它，然后转向下一个。模型会在单个文件里帮忙，但文件之间的连接仍要记在脑子里。
一旦编辑能一次跨越多个文件，工作单元就变了。模型能把整个变更看作一个形状，于是我开始按功能的边缘来规划，而不是按它的中心。
改变了什么
- 功能被规划为一个形状
- 文件之间更少的手动连接
- 更快尝试一个方向
- 推翻一个决定的代价更小
最大的转变不是速度。而是一次变更的边界不再是一个文件。
2026-07-19build-loginmydraft
多文件编辑改变了我构建的方式
一次性编辑多个文件改变了我规划功能的方式。一次变更的形状比其中任何单个文件的大小更重要。
更多更新
general2026-10-03
Checkout Flow Acceptance Criteria That Test Real Behavior
Start checkout flow with the result that must remain trustworthy. That means the work has to keep price authority on the server and connect payment intent, webhook, fulfillment, retry, and receipt. Without that boundary, redirect success alone does not prove…
checkout flowacceptance-criteriapractical guide
阅读
general2026-10-03
Backups Acceptance Criteria That Test Real Behavior
The value of backups appears when the team can explain the decision before discussing implementation. The practical scope is to name the protected data, schedule, retention, encryption, restore owner, and acceptable loss window. The central risk is that a…
backupsacceptance-criteriapractical guide
阅读
general2026-10-02
Accessibility Acceptance Criteria That Test Real Behavior
Planning accessibility becomes reviewable only after its state, owner, and failure boundary are visible. In practice, the team needs to define keyboard order, focus visibility, semantics, labels, errors, contrast, zoom, and reduced-motion behavior.…
accessibilityacceptance-criteriapractical guide
阅读