知识卡片

普通读书笔记卡 · 1971.o.1.b.1.a.2.c.4

保留专业方言也要核算翻译成本

理解等级:高级

同一企业的不同群体可能有各自精确的术语。若强推一套语言,培训和差异消解成本可能很高,统一词汇还可能失去专业精度;可让方言留在不同上下文,并在必要接口翻译,重叠多时考虑共享内核。

但拆分会降低共同沟通、增加翻译与重复建模。要追问术语差异是否真的有价值,不能用“专业化”给任意怪异模型找借口。深层统一模型若后来出现,可以再重构;原书明确说不能预先指望它必然出现。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    参考来源

    - 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第114章《Choosing Your Model Context Strategy》(源文件:_epub-src/0321125215_ch14lev1sec13.html;单元03) - 结论依据:原文同时列出专业术语的价值和分离模型的沟通、翻译、重复成本,并警惕以术语特殊性合理化无价值差异。 - 原始内容:Different groups within the same business have often developed their own specialized terminologies, which may have diverged from one another. These local jargons may be very precise and tailored to their needs. Changing them (for example, by imposing a standardized, enterprise-wide terminology) requires extensive training and analysis to resolve the differences. Even then, the new terminology may not serve as well as the finely tuned version they already had. [...] Different dialects of the UBIQUITOUS LANGUAGE will evolve around these models and the specialized jargon they are based on. If the two dialects have a lot of overlap, a SHARED KERNEL may provide the needed specialization while minimizing the translation cost. [...] The loss of shared language will reduce communication. There is extra overhead in integration. There will be some duplication of effort, as different models of the same business activities and entities evolve. But perhaps the biggest risk is that it can become an argument against change and a justification for any quirky, parochial model. How much do you need to tailor this individual part of the system to meet specialized needs? Most important, how valuable is the particular jargon of this user group? You have to weigh the value of more in-dependent action of teams against the risks of translation, keeping an eye out for rationalizing terminology variations that have no value. Sometimes a deep model emerges that can unify these distinct languages and satisfy both groups. The catch is that deep models emerge later in the life cycle, after a lot of development and knowledge crunching, if at all. You can't plan on a deep model; you just have to accept the opportunity when it arises, change your strategy, and refactor. - 摘录说明:两处 `[...]` 标明分开上下文建议与局部术语保留条件的省略;原 EPUB 列表项抽取重复,现每项只引一次。`in-dependent` 为 EPUB 正文断词,保留以便定位;正文按 independent(独立行动)理解。