知识卡片
优先柔化复杂核心
大型系统很难处处达到易懂、易组合、易修改的柔性状态。当复杂性已阻碍进展,应先找出最关键且最难变的领域部分,反复提炼其模型和接口,让后续修改与试验在这里更容易开展。这是作者的经验性优先级,而非能保证每个项目成功的固定配方;其余部分可按实际价值逐步处理。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Chapter Ten. Supple Design · 查看原书依据
Early versions of a design are usually stiff. Many never acquire any suppleness in the time frame or budget of the project. I've never seen a large program that had this quality throughout. But when complexity is holding back progress, honing the most crucial, intricate parts to a supple design makes the difference between getting sucked down into legacy maintenance and punching through the complexity ceiling.
参考来源
- 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第72章《Chapter Ten. Supple Design》(源文件:_epub-src/0321125215_ch10.html)
- 结论依据:原文承认大型程序难以全局柔性,建议在复杂度压制进展时打磨最重要且错综复杂的部分,并明言没有通用公式。
- 原始内容:Early versions of a design are usually stiff. Many never acquire any suppleness in the time frame or budget of the project. I've never seen a large program that had this quality throughout. But when complexity is holding back progress, honing the most crucial, intricate parts to a supple design makes the difference between getting sucked down into legacy maintenance and punching through the complexity ceiling.