When Continue reading this book, I found some remarks which, in my experience now is not yet fully understood, but there are a few I remember very profound point:
Rule of thumb:
1/3 of the time for planning
1/6 for encoding
Means for testing 1/4
1/4 for system testing
This time I have some shocking plan, the original I think the most important encoding time throughout the project is a long time occupied the least, account for only 1/6 of the time; but in our practice is not the same the usually rough plan what we are, but more time is encoded in the program. This defeats the purpose of the user, the user needs only a thorough understanding of, do a fully functional program, in order to have a good project. There is software testing. We do not go far enough yet.
Surgical teams:
1. The same two years experience and in the case subject to the same training, excellent professional programmer productivity is poor programmers times. On this one I have seen in years of extreme programming, Sackman and Humphrey were done excellent work efficiency was found relatively poor programmer programmer productivity up to a maximum of 28 times.
2. small, elite team is the best. This software processes and Extreme Programming in have been fully reflected.
3. The two-person team, one of the project managers, often the best method to use.
4. For large systems in the true sense, a small elite team too slow.
5. In fact, the experience of the vast majority of large-scale programming system shows that swarmed development approach is the high cost, slow, inadequate, develop products can not be integrated in the concept.
6. a chief programmer, similar to the surgical team team structure provides a way to access to both the integrity of the product produced by a few minds, but also get a number of support staff overall productivity, but also drastically reduces the workload of communication.
Aristocratic despotism, democracy and system design:
1. The concept of integrity is the most important system design considerations.
2. In order to achieve conceptual integrity, must be designed by a single person or a small team to complete consensus.
3. For very large project, design methods, working with the specific implementation of the phase separation structure is a powerful method of obtaining integrity concept.
4. discipline, rules on the industry is beneficial. External architecture has the effect of enhancing rather than limiting creativity to achieve the group.
The architecture, design and implementation, a number of physical implementation may work concurrently.
Superfluous:
1. exchange as soon as possible and continue to make structural engineers communicate better cost-conscious, and enables developers to gain confidence in design and does not confuse the respective responsibilities.
2. The impact of structural engineers how to successfully achieve:
. I keep in mind is to assume responsibility for achieving creative developer; structural engineers can only make recommendations.
ii. the advice of developer improvements in the architecture.
3. The second system is the most dangerous people in the system design, the usual tendency to be overly designed. To this may be true, but this is a problem that can not be avoided, if not developed a second system experienced people, there can be no third system development experience of people.