Books/Code complete

Chapter 2
Use of metaphors for better software development

1. Farming metaphor (used for small incremental development) 2. Building metaphor (includes formal planning,blueprint)

Chapter 2
"Measure twice, cut once" - Worst software projects tend to construct code three or more times

- Have a better problem definition! Problem definition must have the problem not the solutions - Have an official requirement document - Avoids argument - "Requirements are like water. They're easier to build on when they're frozen." - Handling changes in the requirement - Remind them about "cost" involved and the need for revising the "schedule" as it is not in requirement document - Inform every one about the change

Chapter 5
- Creating high quality code