By reading the seventh of eight chapters, I learned that the code is not perfect, none of the code does not require an increase in anything. Because people always pursue the ultimate function. Hang demand, we have to do is tap the demand, and build your customer requirements document together, we have to remember that demand is not architecture, not a demand is not designed interface, demand is required.
Pragmatic project requires a pragmatic team. Focus on quality, quality comes from all team members can only make its own contribution. To ensure that changes everyone proactive monitoring environment. Team of developers must communicate with each other. Writing is a very important part of what was written. Comments in the code, an essential thing, he can get those hard to describe, easy to forget, but can not record things written down in any other place. A good code has a great expectations. AC expectations, a user may start with their imagination of what needed to walk in front of you, but it may be incomplete, inconsistent, or impossible. So the exchange is desirable to have a great significance for the user to achieve the desired functionality. While sharing their expectations and to share what you're doing with them. They managed to get surprised.