《高效代码：软件编程实践原则》是一本致力于提高软件编程效率和优化代码质量的技术书籍。本书探讨了编程中常见的复杂性问题，并提供了一系列切实可行的实践原则与方法。本书内容涵盖了从控制代码复杂性、应用设计原则，到模块化编程、性能优化等多个方面。书中不仅讲解了如何编写高效、可维护的代码，还强调了遵循编程规范、优化代码结构、实施测试驱动开发等最佳实践，帮助开发者在保证代码质量的同时提高开发效率。 本书适合软件开发者，尤其是中高级开发者。对于初级开发者，书中的设计原则和实践经验可助其打下扎实的编程基础，掌握管理代码复杂性和编写高质量代码的方法；对于有一定经验的开发者，书中的深入分析提供了应对项目中挑战的思路，如提高代码质量、优化架构设计和加强团队协作等。书中的实用建议是每位开发者值得参考的编程指引。
独道东，从事软件架构与研发工作14年。曾在东软、IBM、百度等互联网IT科技公司任职，积累了丰富的行业经验。自2016年起，加入北京金山云科技有限公司，现担任公有产品云研发中心研发专家，负责金山云计算与云存储Web控制台及资源管理业务中台的架构设计与研发工作。在此期间，我主导了多个项目的落地与实施，推动了云计算与存储平台的高效运作。我热衷于技术创新，个人拥有两项软件著作权和一项正在审批中的专利。此外，我积极参与开源社区的贡献，作为Go语言工具函数库Lancet（GitHub中文排名第1）的作者，致力于通过开源项目推动技术的普及与应用。通过持续的学习与实践，我不断提升自己的技术能力和架构设计水平，始终保持对技术的热情与追求。
第1章 直面软件复杂性 ·······················.1
1.1 代码为什么会越来越混乱 ···········.1
1.2 复杂性的真相 ··························.1
1.3 复杂性无处不在 ·······················.3
1.4 你的代码正在失控 ····················.4
1.5 为什么简单的代码会变复杂 ········.6
1.6 控制复杂性的策略 ····················.7
1.7 小结 ····································.10
第2章 遵循设计原则 ························.11
2.1 单一职责原则 ························.11
2.1.1 未遵循单一职责原则的代码示例 ·····················.12
2.1.2 遵循单一职责原则的代码示例 ···························.14
2.2 开放封闭原则 ························.17
2.2.1 未遵循开放封闭原则的代码示例 ·····················.17
2.2.2 遵循开放封闭原则的代码示例 ···························.18
2.3 里氏替换原则 ························.20
2.3.1 未遵循里氏替换原则的代码示例 ·····················.21
2.3.2 遵循里氏替换原则的代码示例 ···························.22
2.4 接口隔离原则 ························.23
2.4.1 未遵循接口隔离原则的代码示例 ·····················.24
2.4.2 遵循接口隔离原则的代码示例 ···························.25
2.5 依赖倒置原则 ························.27
2.5.1 未遵循依赖倒置原则的代码示例 ·····················.28
2.5.2 遵循依赖倒置原则的代码示例 ···························.29
2.6 迪米特法则 ···························.30
2.6.1 未遵循迪米特法则的代码示例 ···························.32
2.6.2 遵循迪米特法则的代码示例 ···························.33
2.7 设计原则并非教条 ......................... 36
2.8 小结 ................................................. 36
第3章 遵守编程规范 ·························.38
3.1 编程规范的多维内涵 ···············.38
3.2 编程规范的重要性 ··················.39
3.3 编程规范核心要素解析 ············.41
3.4 制定高效编程规范 ··················.43
3.5 规范执行比规范本身更重要 ······.47
3.6 解读业界优秀编程规范 ············.49
3.7 小结 ····································.50
第4章 编写可维护性代码 ···················.51
4.1 为什么“代码可运行”远远不够 ··.51
4.2 什么是可维护性代码 ···············.52
4.3 如何编写可维护性代码 ············.55
4.3.1 命名的艺术：让变量和函数自述身份 ·····················.55
4.3.2 掌控逻辑控制流程和数据流向 ···························.60
4.3.3 设计包结构 ··················.67
4.3.4 异常管理 ·····················.76
4.3.5 提高代码的可测试性 ······.80
4.3.6 使用设计模式 ···············.85
4.4 代码评审 ······························.86
4.5 小结 ····································.89
第5章 模块化编程 ···························.90
5.1 模块：分而治之 ·····················.90
5.2 接口：连接的桥梁 ··················.91
5.3 抽象：提取共性，减少重复 ······.95
5.4 深模块和浅模块 ·····················.96
5.4.1 深模块 ························.96
5.4.2 浅模块 ························.97
5.5 封装和信息隐藏 ·····················.98
5.6 组合优于继承 ························.99
5.7 依赖注入和控制反转 ··············.103
5.8 小结 ···································.108
第6章 代码是数据的映射 ·················.109
6.1 以业务逻辑为核心的编程 ········.109
6.2 以数据结构为核心的编程 ········.111
6.3 应用数据结构优化代码 ···········.114
6.3.1 基本数据结构 ··············.115
6.3.2 高效使用Map结构 ·······.119
6.3.3 使用结构体优化重复代码 ··························.121
6.3.4 使用接口优化代码扩展性 ·······················.122
6.4 业务逻辑驱动编程和数据结构驱动编程 ·····························.124
6.5 小结 ............................................... 124
第7章 选择编程范式 ·······················.125
7.1 什么是编程范式 ····················.125
7.2 为什么要掌握编程范式 ···········.125
7.3 编程范式分类 ·······················.126
7.4 主流编程范式解析 ·················.128
7.4.1 过程式编程 ·················.128
7.4.2 面向对象编程 ··············.132
7.4.3 函数式编程 ·················.137
7.4.4 逻辑式编程 ·················.142
7.4.5 编程范式对比 ··············.145
7.5 对编程范式的思考 ················.146
7.6 小结 ··································.147
第8章 分离业务逻辑和技术实现 ········. 148
8.1 业务逻辑和技术实现 ·············.148
8.2 分离业务逻辑代码和技术实现代码 ··································.150
8.3 关注点分离 ·························.151
8.4 领域驱动设计：解耦业务逻辑的利器 ··································.153
8.4.1 什么是领域驱动设计 ····.153
8.4.2 领域驱动设计的关键概念 ·························.153
8.4.3 应用领域驱动设计分离业务逻辑和技术实现 ····.156
8.5 实践中的挑战和解决方案 ·······.162
8.6 小结 ··································.163
第9章 测试驱动开发 ·······················. 165
9.1 软件测试概述 ······················.165
9.2 让测试成为编码的起点 ··········.168
9.3 单元测试实践 ······················.169
9.3.1 单元测试的优势 ··········.169
9.3.2 如何编写单元测试 ·······.170
9.4 小结 ··································.182
第10章 优化代码性能 ·····················.183
10.1 性能优化时机 ·····················. 183
10.2 数据驱动的优化决策 ············. 184
10.3 性能优化策略 ·····················. 186
10.4 性能优化实践 ·····················. 188
10.4.1 优化计算效率············.189
10.4.2 优化内存资源············.193
10.4.3 优化I/O操作 ············.197
10.5 代码可维护性和性能的平衡 ···. 202
10.6 小结 ·································. 202
第11章 持续重构代码 ·····················.204
11.1 重构为代码注入生命力 ·········. 204
11.2 为什么重构不可忽视 ············. 205
11.3 何时重构 ···························. 206
11.4 重构实践 ···························.209
11.5 识别代码的“坏味道” ·········.211
11.5.1 重复代码 ··················.211
11.5.2 长函数 ·····················.214
11.5.3 过长的参数列表 ·········.216
11.5.4 过大的类 ··················.217
11.5.5 过长的消息链 ············.219
11.5.6 冗余类 ·····················.220
11.5.7 过度抽象 ··················.222
11.5.8 神秘命名 ··················.223
11.5.9 隐式依赖 ··················.224
11.6 重构和重写 ························.225
11.7 小结 ·································.225
第12章 文档、注释和知识共享 ··········.226
12.1 让文档成为团队的知识库 ······.226
12.1.1 文档的必要性 ············.226
12.1.2 明确文档类型 ············.227
12.1.3 文档的结构和组织······.234
12.1.4 文档的维护和更新······.236
12.1.5 提高文档的可访问性和易用性·····················.236
12.2 让注释为代码加分 ···············. 237
12.2.1 统一注释格式············.238
12.2.2 注释阐明代码意图，而非代码内容············.240
12.2.3 注释描述代码中不明显的部分·····················.242
12.2.4 区分低级注释和高级注释························.244
12.2.5 同步更新注释和代码···.246
12.3 知识共享和团队协作 ············. 247
12.3.1 促进知识共享············.247
12.3.2 提高团队协作效率······.249
12.4 小结 ·································. 250
书单推荐
