Extreme programming - the way to practice as a programmer

• Chapter1 How to practice as a programmer
• 1-1 The code was eaten by the cat
• 1-2 Broken Windows and Stone Soup
• 1-3 evil repetition
• 1-4 Excellent design
• 1-5 Software that is good enough - "There is no perfect product in the world - don't ask for the best, just be good enough"
• 1-6 Orthogonality: How to crack a project that affects the whole world
• 1-7 "Tofu dregs" project can actually be used as a prototype
• 1-8 Agile estimating
• 1-9 Don't run out of headlight range
• 1-10 tracer
• 1-11 Reversibility
• 1-12 Dead programs don't lie
• 1-13 version control
• 1-14 ruthless testing
• Chapter2 Extreme Programming Series
• 2-1 On the importance of code specifications (Part 1)
• 2-2 How to pair up in pair programming
• 2-3 On the importance of code specifications (Part 2)
• 2-4 Why implement collective code ownership?
• 2-5 The secret behind the Linux kernel project’s 30-year survival
• 2-6 user stories
• 2-7 planning game
• 2-8 On-site customers
• 2-9 system metaphor
• 2-10 40 hours
• 2-11 Simple design
• 2-12 test driven development
• 2-13 Refactor