目录
1. 编程的精义
1. 编程的精义······················································· 11
2. 会或者不会写程序············································· 13
3. 程序= 算法+ 结构········································ 14
4. 语言·································································· 16
5. 在没有工程的时代············································· 16
2. 是懒人造就了方法
1. 是懒人造就了方法············································· 18
2. 一百万行代码是可以写在一个文件里的············ 20
3. 你桌上的书是乱的吗········································· 23
4. 我的第一次思考：程序=算法+结构+方法·········· 25
3. 团队缺乏的不只是管理
1. 三个人的团队···················································· 29
2. 做项目= 死亡游戏?······································· 31
3. 做ISO 质量体系的教训····································· 33
4. 谁动摇了你的制度？ ········································· 36
5. “那我们就开始开发吧” ·································· 38
6. 组织的学问：角色············································· 39
7. 跟随蚂蚁。但不要栽进蚂蚁洞里。··················· 42
8. “什么是增值税发票？” ·································· 44
4. 流于形式的沟通
1. 客户不会用C，难道就会用UML 吗？·············· 48
2. 项目文档真的可以用甲骨文来写······················· 50
3. 最简沟通··························································· 53
4. 为不存在的角色留下沟通的渠道······················· 57
5. 流于形式的沟通················································ 60
5. 失败的过程也是过程
1. 做过程不是做工程············································· 63
2. 做过场······························································· 65
3. 实现，才是目的················································ 65
4. 过程不是死模型················································ 66
5. “刻鹄类鹜”与“画虎类狗” ·························· 69
6. 工程不是做的，是组织的·································· 71
6. 从编程到工程
1. 语言只是工具···················································· 73
2. 程序·································································· 75
3. 方法·································································· 75
4. 过程·································································· 76
5. 工程·································································· 78
6. 组织·································································· 80
7. BOSS································································· 82
8. 上帝之手··························································· 84
7. 现实中的软件工程
1. 大公司手中的算盘············································· 87
2. 回到工程的关键点············································· 92
3. 思考项目成本的经理········································· 94
4. 审视AOP ·························································· 97
5. 审视MDA ························································100
8. 是思考还是思想
1. 软件工程三个要素的价值·································103
2. 其实RUP 是一个杂物箱···································104
3. UML 与甲骨文之间的异同·······························105
4. 经营者离开发者很远，反之亦然······················106
5. 矛盾：实现目标与保障质量·····························107
6. 枝节与细节······················································108
7. 灵活的软件工程···············································110