Read << People's Month myth >>

The book is very well known in software, and is highly recommended every time you see an article that is recommended in the year. It has been published for 30 years and is a classic.

But I was not so deep in the process of reading. Many of the chapters in the book are based on the experience of large-scale projects or large-scale systems, and so far I have not participated in projects that are larger than 30 people. It is not enough to say that you are a state.

The first chapter, tar Pits

Can never find a word more descriptive than tar pits, the process of software development. We are all struggling. Plan, plan, keep planning, but procrastinate, procrastinate, procrastinate ....

Career fun: Creativity, contribution to helping others, the charm of the process or the satisfaction of solving a problem or the thrill of writing code, continuing to learn new things and harness the senses.

Occupational distress: The Pursuit of perfection, by others set goals and requirements, repetition, pay and harvest is not proportional to, even no harvest.

Chapter II, Human-moon mythology

The main reason for project lag: lack of reasonable schedule. lack of effective research on estimating techniques, mistakenly confuse progress and effort with each other
Estimating lack of confidence
Lack of tracking and oversight of progress
When you are aware of the progress of the offset, the wrong increase in manpower.

Chapter III, surgical teams

This chapter is about the team and, in general, what kind of team to build. There is no best team, only the most suitable team.

Fourth chapter, aristocratic autocracy, democratic politics and system design

This chapter is in fact the boss has always told me that consistency, integrity. I didn't understand, after more than a year of practice, now understand that consistency is important, very important. Directly determines the extensibility, readability, reusability of the code.

Fifth chapter, The Lily, the sixth chapter, the implementation

The division of the team, the responsibility of the divisions.

The seventh chapter, why Babel will fail?

Because there is no communication, no organization.

I now realize that the highest cost in a project is communication. Communication directly affects the progress of the project, even the direction.

Documents are important, and documents can be used as a basis for communication. The basis of the organization structure.

The eighth chapter, the fits, the Nineth chapter, the ... to the 15th chapter.

16th chapter, no silver eggs

The most classic chapter, the core problem of software development is complexity.　　

The prototype is very important. Fast Prototype fast iteration.

Read << People's Month myth >>