The feeling of reading "The Myth of Man and Month"

The teacher recommended this book to read a great harvest, here to share their own sentiment. First of all, I feel that the field of software engineering is a new field, the prospect of development is very broad, the impact on society is also the Abyss, the Book of the People of the month myth author from his experience in the practice of his own views, from the author of his experience in the Readme I found that the author is not all the way flat have success has failed but The development of large systems over the past few decades is like such a tar pit, where only a very small number of projects meet the requirements of goals, time schedules and budgets. A variety of teams, large and small, complex and lean, one by one submerged in the tar pits. "Indeed, many of the failures in previous examples are like drowning in tar pits, and it is true that there are a lot of small programmers who are not very modest but through simple teams, the simple environment has also produced large-scale software with great economic benefits, This embodies the idea of people's month myth, the deployment of staff and time is the efficiency, we all can from the success of the compilation of fun, because it gives us a sense of accomplishment, we have done something useful to others, on the contrary, a software always have the error can not be found will let us be interested, and I can always feel that they are not perfect has been pursuing more perfect, we should be effective in estimating technology, it allows us to not produce the assumption that everything will work well, this unreal hypothesis will hit our confidence, when our progress is offset, blindly increase the manpower will make things worse, resulting in a vicious circle, This tells us the importance of progress, in my programming process there is also an optimism, often think that this is the last mistake I will succeed, but the error is followed by a concept and a flexible form of expression to develop the program. Due to the ease of the media, we look forward to not encountering difficulties in the implementation process, thus creating a pervasive optimism. Our ideas are flawed, that is to say, our optimism should not be taken for granted. It is very important to arrange the time reasonably, and to make reasonable and correct planning arrangements for the time in combination with the customer requirements and the actual project. The surgical team embodies the fact that the soldiers are expensive, the difference between good programmers and the average programmer, the number of people who need to work together affects the cost of development, because the main component of the cost is mutual communication and communication, as well as correcting bad results caused by improper communication (System debugging). This also implies that the system should be developed by as few people as possible. In fact, the experience of most large programming systems shows that swarmed's development approach is costly, slow, and inadequate, and is best designed and developed by a handful of skilled personnel for the integrity of efficiency and concepts, while large systems require a large number of manpower to enable the product to meet the requirements in time. , in the recommendations of the Harlan Mills the staffing should be like a surgical procedure, by a person to do the decomposition of the problem, others give him the support needed to improve the effectivenessEfficiency and productivity, and in the distinction between the traditional two-person team and the surgeon-deputy team structure, the traditional team divides the work, each of which is responsible for the design and implementation of part of the work. In the surgical team, surgeons and deputies know all about the design and all the code. The effort to save space allocation, disk access, and so on, does ensure the conceptual integrity of the work, the differences between the two teams--that the problem is not broken down and that the level of the hierarchy allows the surgical team to achieve objective consistency. Conceptual consistency reflects a complete set of ideas that omit some irregular features and improvements, and do not advocate for independent and non-integrated systems, even if they actually contain many good designs, and the recommendations of the goals require that we try to make the functional descriptions concise and easy to understand. In short, the author of the book, combined with personal experience to explain to us a classic case, thought-provoking for me this kind of programming beginners have a lot of guidance, some of them have also experienced some is going to experience, there is a great guiding role.

Read "The myth of the People's Month"