Update nexus: fix conflicts and sync local changes
This commit is contained in:
@@ -1,28 +1,28 @@
|
||||
---
|
||||
title: "DRY原则"
|
||||
type: concept
|
||||
tags: [software-engineering, coding-standards, best-practices, dry]
|
||||
sources: [开发经验与项目规范整理文档]
|
||||
last_updated: 2025-12-30
|
||||
---
|
||||
|
||||
## Definition
|
||||
|
||||
**DRY 原则(Don't Repeat Yourself)** 是一种软件开发原则,核心思想是:系统中的每一片知识都必须有一个单一、明确、权威的表述。避免重复代码,提炼公共逻辑,提高复用价值。
|
||||
|
||||
## Core Principles
|
||||
|
||||
- 消除重复代码
|
||||
- 提炼公共逻辑到可复用模块
|
||||
- 保持代码的单一事实来源
|
||||
- 通过抽象和模块化实现代码复用
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[单一职责原则]] — DRY 的前提是模块有清晰的职责
|
||||
- [[模块化编程]] — DRY 的实现手段
|
||||
- [[Vibe Coding]] — AI 辅助开发中避免重复生成相似代码的指导原则
|
||||
|
||||
## Source Reference
|
||||
|
||||
来源:[[开发经验与项目规范整理文档]]
|
||||
---
|
||||
title: "DRY原则"
|
||||
type: concept
|
||||
tags: [software-engineering, coding-standards, best-practices, dry]
|
||||
sources: [开发经验与项目规范整理文档]
|
||||
last_updated: 2025-12-30
|
||||
---
|
||||
|
||||
## Definition
|
||||
|
||||
**DRY 原则(Don't Repeat Yourself)** 是一种软件开发原则,核心思想是:系统中的每一片知识都必须有一个单一、明确、权威的表述。避免重复代码,提炼公共逻辑,提高复用价值。
|
||||
|
||||
## Core Principles
|
||||
|
||||
- 消除重复代码
|
||||
- 提炼公共逻辑到可复用模块
|
||||
- 保持代码的单一事实来源
|
||||
- 通过抽象和模块化实现代码复用
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[单一职责原则]] — DRY 的前提是模块有清晰的职责
|
||||
- [[模块化编程]] — DRY 的实现手段
|
||||
- [[Vibe Coding]] — AI 辅助开发中避免重复生成相似代码的指导原则
|
||||
|
||||
## Source Reference
|
||||
|
||||
来源:[[开发经验与项目规范整理文档]]
|
||||
|
||||
Reference in New Issue
Block a user