知识卡片
可执行代码检验架构细节
可运行的代码让架构讨论承担具体细节:接口怎样连接、状态怎样传递、概念中的省略能否真正实现,都必须被说明。它既是表达手段,也是检验概念是否足够精确的工具。
代价是示例必然绑定语言和产品,而且版本会过时。阅读时应把实现用来检验机制,另外辨认哪些判断来自通用约束、哪些只是该工具的实现选择。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 前言:从业务痛点理解自动化 · 查看原书依据
Discussing concepts is only half the fun if you cannot point to concrete code examples. Runnable code forces you to be precise, to think about details you can leave out on the conceptual level—and, most importantly, it often explains things best. I am personally a big fan of the motto “the architect always implements.”
参考来源
- 位置:《Practical Process Automation (Bernd Ruecker)》附加正文《Preface》(来源项目:book-sources;源文件:extracted/Practical Process Automation (Bernd Ruecker)/_epub-src/OEBPS/preface02.xhtml)
- 结论依据:原文给出本卡所述区别及具体作用;正文的适用提醒据此限定,不外推为普遍必然。
- 原始内容:Discussing concepts is only half the fun if you cannot point to concrete code examples. Runnable code forces you to be precise, to think about details you can leave out on the conceptual level—and, most importantly, it often explains things best. I am personally a big fan of the motto “the architect always implements.”