(Book gift at the end of the article) Why do I recommend that everyone should get a copy of "The Myth of the Man and the Moon"

If you can click in, it means that you must be a friend who works in computers or is thinking carefully about this book.

1. In an era where everyone can program, how do we survive?

    I was reading a book 《人月神话（纪念典藏版）》, and I remember a passage in the book:

回首软件工程近40年的发展，Jackson哀叹软件行业普遍缺乏专业性，充满了业务人员，“手中有一个锤子，看到什么都是钉子”，谁都可以开发性命攸关的软件。

If 1,000 people see this passage, there will definitely be 1,000 different comments and thoughts. After I understood it deeply, I suddenly realized that it makes sense. my comment:

• Although we are in the era of programming now, primary school students are learning it, junior high school students are learning it, high school students are learning it, college students are still learning it, and even children in kindergarten are learning building block programming. I often see various advertisements promoting Python tutorials, and I always click on them to see what they contain. There are many Python courses for people who are not computer majors. They promise to save you a lot of time after learning them. For example, you can make reports and the like. Some of them are very tricky, so I won’t go into detail here.

• 现在的趋势已经非常明显了，正在朝着人人都必须会编程的时代发展，我们如何立足是个值得思考的问题。

• The excerpt above allows us to reflect on how to survive in an era where everyone can program. The answer is also in this passage, which can be summarized in two or three words: professionalism.

• 没错，现在就是缺乏专业性的软件开发人员. (Please continue reading and you will discover the new world)

2. A short story explains why project managers must read this book

    In XXX company, there is a middle-aged programmer named Lao Wang. He dreamed of developing an application that could help villagers buy and sell vegetables, and is now the person in charge of the project. In order to complete the project faster, the company boss suggested that he hire more programmers.

    Excited, Lao Wang started working with his team.但随着时间的推移，她发现项目进展缓慢，团队成员之间的沟通变得越来越复杂。老板看到项目滞后，建议他再招聘一些程序员。但令人意外的是，这只使情况变得更糟。

    Lao Wang was confused. He thought that with more programmers, he could complete the work faster. But the reality was far from what he expected.

    At this time, an old programmer in the town gave him a book "The Myth of the Man and the Moon". Lao Wang suddenly realized it after reading it.他从中学到了软件项目的复杂性，了解了为什么仅仅增加更多的人手并不能解决问题，甚至可能导致更多的问题。

    老王按照书中的建议调整了团队结构，更加注重沟通和计划，最终成功完成了他的项目。

    Both the boss and the users are very satisfied with this application. And Lao Wang deeply understood why every software engineer should read "The Myth of the Man-Month".

This story highlights the importance of The Mythical Man-Month to understand the challenges in project management, especially when it comes to human factors and team dynamics.

3. How to evaluate "The Myth of the Man-Month: Commemorative Collector's Edition"

"The Mythical Man-Month: Anniversary Edition" (The Mythical Man-Month: Anniversary Edition) is a follow-up version of the original version of "The Mythical Man-Month". Based on the 1975 edition by Frederick P. Brooks, the new book adds new chapters and content. Here are some main points and thoughts after reading "The Myth of the Man-Month: Memorial Collector's Edition":
Main points :

1. The Man-Month Myth : Reinforces the idea that adding people to a lagging project will only cause it to lag further.
2. No Silver Bullet : The belief that there is no single solution that can drastically improve software development productivity.
3. Conceptual Integrity : Emphasizes the importance of consistency and a single vision in product design.
4. Redo rather than fix : It is recommended that a system design be completely redone on the first try rather than simply fixed.
5. Communication and documentation : As the size of your team grows, so does the cost of communication.
6. Intangibility of software : The progress and complexity of software products are difficult to visualize, unlike physical products.
7. Premature optimization : Focus on the correctness and clarity of the product first, and then consider optimization.
8. Interaction between technology and people : Emphasizing the importance of human factors in software development.
9. Challenges of Large Projects : There are fundamental differences between large projects and small projects.
10. New chapters : The commemorative collector's edition adds a re-evaluation and reflection on the original book's ideas.

Possible thoughts after reading :

1. Test of time : The author's ideas remain relevant even decades later, which shows the depth and durability of his insights.
2. Human Factor : Software development is not just about code or technology, the interaction between people and teams plays a key role in project success.
3. The Complexity of Project Management : This book provides insight into why software projects are often late and over budget, ideas that still hold true in the modern era.
4. Reflection and Learning : Brooks's self-reflection and evaluation of original ideas in this commemorative edition demonstrate the self-critical spirit that a true scholar and practitioner should possess.
5. Inspiration and Guidance : For software engineers and project managers, this book provides valuable insight and guidance to help them avoid common pitfalls and manage projects more effectively.

After reading the commemorative collector's edition, many readers may be deeply inspired and apply the author's views and experiences to their own work.

4. The table of contents of this book (you can take a look at the table of contents that I finally pulled out)

Just look at the catalog and you will be attracted to it. Don't worry, I'll send you a copy soon.
Just look at the catalog and you will be attracted to it. Don't worry, I'll send you a copy soon.
Just look at the catalog and you will be attracted to it. Don't worry, I'll send you a copy soon.

目　录
第1章 焦油坑 / 001
编程系统产品 / 003
职业的乐趣 / 005
职业的苦恼 / 006
第2章 人月神话 / 009
乐观主义 / 011
人月 / 013
系统测试 / 016
空泛的估算 / 018
重复产生的进度灾难 / 019
第3章 外科手术队伍 / 025
问题 / 027
Mills的建议 / 029
如何运作 / 032
团队的扩建 / 033
第4章 贵族专制、民主政治和系统设计 / 035
概念的完整性 / 037
获得概念的完整性 / 038
贵族专制统治和民主政治 / 039
在等待时，实现人员应该做什么 / 042
第5章 画蛇添足 / 047
结构师的交互准则和机制 / 049
自律—开发第二个系统所带来的后果 / 050
第6章 贯彻执行 / 055
文档化的规格说明—手册 / 057
形式化定义 / 058
直接整合 / 061
会议和大会 / 061
多重实现 / 063
电话日志 / 064
产品测试 / 064
第7章 为什么巴比伦塔会失败 / 067
巴比伦塔的管理教训 / 069
大型编程项目中的交流 / 070
项目工作手册 / 070
大型编程项目的组织架构 / 074
第8章 胸有成竹 / 079
Portman的数据 / 082
Aron的数据 / 083
Harr的数据 / 084
OS/360的数据 / 085
Corbató的数据 / 086
第9章 削足适履 / 087
作为成本的程序空间 / 089
规模控制 / 090
空间技能 / 092
数据的表现形式是编程的根本 / 093
第10章 提纲挈领 / 095
计算机产品的文档 / 097
大学科系的文档 / 099
软件项目的文档 / 099
为什么要有正式的文档 / 100
第11章 未雨绸缪 / 103
试验性工厂和增大规模 / 105
唯一不变的就是变化本身 / 106
为变更设计系统 / 106
为变更计划组织架构 / 107
前进两步，后退一步 / 109
前进一步，后退一步 / 111
第12章 干将莫邪 / 113
目标机器 / 116
辅助机器和数据服务 / 118
高级语言和交互式编程 / 121
第13章 整体部分 / 125
剔除bug的设计 / 127
构件单元调试 / 129
系统集成调试 / 132
第14章 祸起萧墙 / 137
是里程碑还是沉重的负担 / 139
“其他的部分反正会落后” / 141
地毯的下面 / 142
第15章 另外一面 / 147
需要什么文档 / 150
流程图 / 152
自文档化的程序 / 156
第16章 没有银弹—软件工程中的根本和次要问题 / 163
摘要 / 165
介绍 / 165
根本困难 / 166
以往解决次要困难的一些突破 / 171
银弹的希望 / 172
针对概念上根本问题的颇具前途的方法 / 181
第17章 再论“没有银弹” / 189
人狼和其他恐怖传说 / 191
存在着银弹—就在这里 / 191
含糊的表达将会导致误解 / 192
Harel的分析 / 195
Jones的观点—质量带来生产率 / 201
那么，生产率的情形如何 / 201
面向对象编程—这颗铜质子弹可以吗 / 203
重用的情况怎样 / 205
学习大量的词汇—对软件重用的一个可预见但还没有被预言的问题 / 208
子弹的本质—形势没有发生改变 / 209
第18章 《人月神话》的观点：是与非 / 211
第19章 20年后的《人月神话》 / 235
为什么要出版20周年纪念版本 / 237
核心观点—概念完整性和结构师 / 238
开发第二个系统所引起的后果—盲目的功能和频率猜测 / 240
图形界面的成功 / 243
没有构建舍弃原型—瀑布模型是错误的 / 247
增量开发模型更佳—渐进地精化 / 249
关于信息隐藏，Parnas是正确的，我是错误的 / 254
人月到底有多少神话色彩？Boehm的模型和数据 / 256
人就是一切(或者说，几乎是一切) / 258
放弃权力的力量 / 259
最令人惊讶的新事物是什么？数百万的计算机 / 262
全新的软件产业—塑料薄膜包装的成品软件 / 264
买来开发—使用塑料包装的成品软件包作为构件 / 267
软件工程的状态和未来 / 269
结束语 令人向往、激动人心和充满乐趣的50年 / 271

5. Thank you to the fans who follow me and to you who are following this book. This book is given to you.

• Book delivery rules:

• Winning rules: If you make a good and sincere comment, you will have a chance to win a book;
• Participation method: 把自己的与软件工程的小故事写下来, 也可以写为什么需要这本书, etc. can be written, 放到本文评论区;
• deadline:2023-9月15日20点整；
• Book Mailing: I will, and will tell you in the comments section when it’s over 第一时间在我的QQ社群发通知. 没加QQ社群（）的抓紧加啦.

• It doesn’t matter if you don’t win the prize. You can participate in an internal event and buy it directly. Anyway, it’s not worth a few dozen dollars:

• Book purchase portal: https://u.jd.com/vuzIvEp

JD.com coupon collection address (no threshold coupon 10 yuan):

• APP：https://pro.m.jd.com/mall/active/2Z3HoZGKy5i9aEpmoTUZnmcoAhHg/index.html
• PC：https://pro.jd.com/mall/active/2Z3HoZGKy5i9aEpmoTUZnmcoAhHg/index.html
• Click here to purchase directly