此卡片不在当前主题的阅读序列中,可返回主题继续阅读。
知识卡片
设计模式依赖适用情境
设计模式把反复出现的结构、用途与动机整理成共享语言,经典 GoF 模式分创建、结构、行为三类,共 23 个。它并非可无条件套用的模板;选择前应核对问题情境与意图,否则模式本身也会增加复杂度和技术债。模式的价值在于缩短解释成本,而不在于让代码看起来“更有设计”。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
原书出处
参考来源
- 位置:《Principles of Software Architecture Modernization》第1章《What’s Wrong with Monoliths?》(源文件:`_epub-src/OPS/ch01.xhtml`,归一化正文 [16591:20775))
- 结论依据:原文把设计模式描述为常见结构与共享概念,说明每种模式都有特定情境、意图和动机,并警告无需要或误用会增加技术债。
- 原始内容:Design Patterns are a set of commonly found patterns in software architecture, describing frequently found structures and designs, and providing a set of shared words and concepts to facilitate communication. Patterns 8 are divided into 3 groups: Creational, Structure, and Behavior, and became very popular in languages like Java, C++, and Smalltalk. The original GOF book has 23 classical patterns, but hundreds of patterns exist in software engineering;