This time, I saw three books of software engineering. "People", "Moon Myth", "Last Term". The first thing to watch is "Moon Myth", which is very impact on my thinking. I called it as a "design pattern" to hit the biggest book. The two two are also classic.
Several books say that if you manage a project. "Month" should be said to be the most comprehensive and compare the authority. Among them, there is a comprehensive description of the plan, personnel configuration, increase manpower, quality, etc. Can be seen as "project manager's speed". "Human Pie" lets us look at the problem of developer psychology, and put the enthusiasm, team building as a very important factor. I remember that after I finished "Moon", a netizen recommended me to see "people", all of which complement each other, indeed good. The "deadline" is a unique way, telling stories to start, how to control a project. However, I feel that this project is still some ideal: he has sufficient manpower, including a large number of adjustable programmers, as well as various excellent professionals. More more is: his project does not need to analyze, nor does it require communication with customers. Haha, this project is probably very little. However, it is indeed a good book.
I believe in others, one can be recognized as a classic book, you can gain it.
Look at "Month", my feelings, including the desire to elite team, more emphasis on quality control, thinking about increasing humanival. And "people" is full respect for each individual, and people don't just work, accomplish, comfortable. It is recommended that all bosses go to see this book. Also, listening to music programming, huh, you can listen, but you can't listen when you are design. And "deadline", don't give the programmer too much pressure, it can't improve work. There is also a minority in the design period, with the development of the project development.
Still analyzing a few books as a whole, because they have been integrated with each other in my head, huh, huh. Plus some of my awareness of XP, summarize a few experience:
1, the quality is the first, do not reduce the quality for the reluctance.
2. As a project manager, the only right may decide which functions do not do (Scope).
3, iterative development, high frequency internal release.
4, do not reach the final stage of the project, absolutely don't work overtime.
5, Play to Win, Not to Avoid Loss.
6, more loose Pair Work, one person basically knows another person's work. The real Pair Work cost is still high.
7, automatic unit test. (Quality assurance)
8, not only to do Code Review, before starting a functional point, you must design a design review to avoid defects or conflicts with other parts.
9. Team, exchange, joint responsibility, can't accuse someone.
10. If a boy-oriented team, there is a ppmm to adjust the atmosphere is very good, huh, huh. This one is I am adding to the integer.
In fact, this time, my most important book is "refactoring", but I haven't finished reading yet. Last week, my spare time contributed to Tang Haoming's "Zeng Guofan". I feel that Zeng Guofan is so hard, finally the people are extremely good, and they are also good, but he is still very uncomfortable, and there is no day for a few days. Instead, it is not as good as Hu, I also took a time to suddenly read it again "Snow Mountain Flying Fox". I feel that Hu Yidao's sincere feelings and rivers and lakes are really fascinating. I have no hope in this life, I hope that my son can come out, such as Hu Yizhe is generally in the style, don't be as tired as Zeng Guofan. My son didn't know how many years would appear. :) "The small matter is long, and the big event is often mistaken for grass." This is a sentence that Zeng Guofan gave me the most impressive. It also applies to IT industry, our leaders can think about this sentence when starting a project.
The pen is moving, I don't know the cloud.
