← 返回刚才阅读的位置

知识卡片

普通读书笔记卡 · 1971.o.1.b.1.a.2.a.1.b.5.e

保险项目过早做通用时区却未用上

理解等级:高级

原书另一个实际理赔系统项目尚未跑过首轮应用,就让长期团队成员预先设计通用时区模型;因需求未明,又投入高级开发者,写出复杂代码,却没有具体应用可验证其正确性。项目后来因多种原因停滞,时区代码从未使用。

作者的“也许只需记录带时区的当地时间,甚至不必转换”是事后推断,并非已实施结果。核心损失是团队未把这些精力用来建立理赔模型与积累保险领域知识。与[[航运项目待需求清楚后才实现时区]]相比,两个项目都正确隔离了通用模型,投入时机与资源配置不同。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 原书第15章|Generic Subdomains · 查看原书依据

      The project ran aground for various reasons, and the time zone code was never used. But if it had been, simply storing local times tagged with the time zone might have been sufficient, even with no conversion, because this was primarily reference data and not the basis of computations. Even if conversion had turned out to be necessary, all the data was going to be gathered from North America, where time zone conversions are relatively simple.

    参考来源

    - 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第119章《Generic Subdomains》(源文件:_epub-src/0321125215_ch15lev1sec3.html;单元04) - 结论依据:原文区分保险项目时区代码未用的实际结果、可能只需简单存储的推断,以及核心域被忽视的机会成本。 - 原始内容:The project ran aground for various reasons, and the time zone code was never used. But if it had been, simply storing local times tagged with the time zone might have been sufficient, even with no conversion, because this was primarily reference data and not the basis of computations. Even if conversion had turned out to be necessary, all the data was going to be gathered from North America, where time zone conversions are relatively simple.