Book Notes - Extreme Programming Explained (2nd Edition)

The main idea of Extreme Programming is that you should not try to predict things and plan everything in detail, but rather use a methodology that embraces changes.

Stay aware. Adapt. Change.

XP is about well-known practices like relentless testing, coding standards, and continuous integration.

But it’s also about some radical programming ideas - on-site customer (to help to guide the decisions), refactoring as a part of the development cycle (rather than upfront design), pair programming, collective code ownership (everyone is responsible for the whole codebase and can change code anytime), flexible planning (pick your goals every day) and design for change (be ready to change anytime).

Even though the ideas from the book are probably not applicable to every situation, I found them inspiring. It definitely broadens my view on how can build software.

Book notes



Pair programming



Single Code Base