…understood (unknown unknowns), which needs to be investigated, even if it turns out not to be a great risk. In agile-speak this is called 'spike solution'. Also see lean architecture methods, such as: - 'Just Enough Software Architecture', by George Fairbanks. - 'Risk and Cost Driven Architecture', by Eltjo Poort.
我想到了乔治·费尔班克斯的那本书《恰如其分的软件架构：风险驱动方法》（Just Enough Software Architecture: A Risk-Driven Approach）。费尔班克斯指出，任何设计都存在风险。它对你的架构该产生多大影响，取决于它对你的项目有多重要。他举了……
George Fairbanks's book _Just Enough Software Architecture: A Risk-Driven Approach_ comes to mind. Fairbanks points out that there's risk in every design. How much it should influence your architecture depends on how much it matters to your project. He uses…
Here is a list so far: - Designing data intensive applications - Just Enough Software Architecture - Domain Driven Design - Tackling Complexity in the Heart of Software (Eric Evans) I recommend this one more than Vaughn Vernon's DDD. - Clean Architecture (Robert Martin) - Fundamentals of Software…
I haven’t seen the risk-driven approach explicitly mentioned here. I think it applies not only to code review, but especially to design. It reminds me of George Fairbanks’ Just Enough Software Architecture. He tells a story about his father, a civil engineer, who didn’t apply every engineering technique he knew when installing a mailbox. He just dug a hole, put in a post, and filled it with concrete. The…
……了解（未知中的未知），这需要去调研排查，哪怕最后证明风险并不大。在敏捷黑话里这叫“探针方案”（spike solution）。另可参考精益架构方法，比如：- 乔治·费尔班克斯（George Fairbanks）的《恰如其分的软件架构》（Just Enough Software Architecture）。- 埃尔特霍·普特（Eltjo Poort）的《风险与成本驱动架构》（Risk and Cost Driven Architecture）。
…understood (unknown unknowns), which needs to be investigated, even if it turns out not to be a great risk. In agile-speak this is called 'spike solution'. Also see lean architecture methods, such as: - 'Just Enough Software Architecture', by George Fairbanks. - 'Risk and Cost Driven Architecture', by Eltjo Poort.
我想到了乔治·费尔班克斯的那本书《恰如其分的软件架构：风险驱动方法》（Just Enough Software Architecture: A Risk-Driven Approach）。费尔班克斯指出，任何设计都存在风险。它对你的架构该产生多大影响，取决于它对你的项目有多重要。他举了……
George Fairbanks's book _Just Enough Software Architecture: A Risk-Driven Approach_ comes to mind. Fairbanks points out that there's risk in every design. How much it should influence your architecture depends on how much it matters to your project. He uses…
这是目前的清单：- 《数据密集型应用系统设计》（DDIA）- 《恰如其分的软件架构》（Just Enough Software Architecture）- 《领域驱动设计：软件核心复杂性应对之道》（Eric Evans著），比起 Vaughn Vernon 的 DDD 我更推荐这本。- 《架构整洁之道》（Clean Architecture，Robert Martin著）- 《软件架构基础》……
Here is a list so far: - Designing data intensive applications - Just Enough Software Architecture - Domain Driven Design - Tackling Complexity in the Heart of Software (Eric Evans) I recommend this one more than Vaughn Vernon's DDD. - Clean Architecture (Robert Martin) - Fundamentals of Software…
我在这里还没看到有人明确提过风险驱动方法。我觉得这不仅适用于 code review，尤其适用于架构设计。这让我想起了乔治·费尔班克斯的《恰如其分的软件架构》。他讲过他父亲的一个故事：他父亲是个土木工程师，但在装邮箱时并没有用上他懂的所有工程技术。他就是挖了个坑，立了根柱子，然后倒满混凝土。这……
I haven’t seen the risk-driven approach explicitly mentioned here. I think it applies not only to code review, but especially to design. It reminds me of George Fairbanks’ Just Enough Software Architecture. He tells a story about his father, a civil engineer, who didn’t apply every engineering technique he knew when installing a mailbox. He just dug a hole, put in a post, and filled it with concrete. The…