Extreme Programming Explained: Embrace Change
Accountability. Transparency. Responsibility. These are not words that are often applied to software development.
In this completely revised introduction to Extreme Programming (XP), Kent Beck describes how to improve your software development by integrating these highly desirable concepts into your daily development process.
The first edition of Extreme Programming Expla...more
In recent years, Agile software development has become such a washed-out term that it's no longer useful if you want to communicate how to develop software. Scrum is more well-defined, but I no longer feel align ...more
- pair programming - all code is written in pairs (on a single computer); this leads to a higher quality of code being written, as the person who is not writing h ...more
Actually, it's a complete rewrite of the first edition.
Actually, it's more like reinventing XP. Kent Beck is adjusting XP so we can benefit from his additional five years of XP experience. The first XP was squarely aimed at programmers; this new version should appeal to everyone involved in software development. The practices have been updated: some have been dropped, some are new. He recommends a much more gradual introduction if you want to move to XP, instead of the st ...more
But I think that this book is just a good one. Just good, but not great. Kent is concise, focused and very deep. But I think he left too much on the reader. Maybe this is just my personal perspective, but I felt that I've missed design consideration from the first edition of this ...more
On the contrary, the process Kent Beck describes as extreme programming sounds like one of the most relaxing, sustainable and rewarding software development frameworks I've heard of. It is of course an ideal, but it seems realistic to be able to approach this ideal. I feel confident in ...more
Objectively, to me it provided
- some very clear (pain)points which can be frequently missed in how the team works and communicates, on how it applies some processes, and how it does its work on a daily basis
- a very good preliminary toolbox from which I can draw ideas on how to handle all ...more
The explanations are really easy to understand and sometimes fun, especially in the early chapters. I really like the steering-a-car analogy on how a development process should be done.
However, again as ...more
After reading the book now I see how Kent thought about planning, estimate, prioritise and maintain the pace, always focusing on the coding part of the equation, but taking into account the busines ...more
The book is not without flaws. The author makes a number of assumptions about people and ...more
Being able to notice, analyze and solve problems outside the code base is part of software engineering.
"Extreme Programming Explained" is the right book for anyone to learn how to do that.
I found every chapter immensely useful although I may have read most of the values and principles in other books or blog posts. The XP scaling and roles is something that the book explained better.
The book chapters ...more
This book does a great job of conveying the practices, principles and values of XP to its target audience. Its style should be familiar to those who have read Kent Beck's other books - it gets right to the point, doesn't repeat itself very much and is split into chapters where they make sense without any artificial bloating of chapters to make them 'the right size' (several chapters are only 2 sides, for example).
"One way a test can pay off is when a test works that you didn't expect to work. Then you better go find out why it works, because the code is smarter than you are." ...more
In the world of silver bullets, buzzwords and markitecture, this book has become more relevant than never. A fundamentally important book on how software should be delivered – values, principles, and practices.
It not only covers technical aspects of XP but also often forgotten ones, like courage and respect.
On the plus side, the book does a good job on clearly laying out the values, principles, and practices of Extreme Programming. I feel that I have a more clear idea in my head of what is meant by this term, and how it relates ...more
What’s so “extreme” about Extreme Programming? First, it advocates a practice called “pair programming” – pr ...more
Many people talk about Agile, CI/CD, Iteration, Incremental development ... but not sure they truly know path on doing those. Not sure they know about the values, principles and especially, the pra ...more
This is why this book is such a refreshment. All ideas & methods he suggests are well argued - reader is not asked to believe him that "his method is the best", rather he shows how & why his recommendations are sensible & useful.
Another great thing that differentiates this book from others in this field, is tha ...more
Anyway, despite being named extreme, there is only very reasonable and common-sensical teachings inside this work, which isn't criticism to it but rather to those who attack it for being "extreme". Beck chose the term because its opposite would seem ...more
It's gives me the same feeling whenever I read about any technology history book, although this is not history per se but it's really full of it, that most of the problems I grapple with aren't new.
I have taken lots of notes and I do have lot of things to share. I will be doing that in a blog post.
The book itself is not completely timeless, it does giveaway the feeling of "past its tim ...more
It offers a framework of values, principles, and practices, that enables more efficient software development and better communication.
At the same time, the author does not dictate which tools must be used or how much time should be dedicated to certain activities.
Instead, the book offers a number of stories that provide a better idea of when and how the framework can be applied.
Personally, I was fa ...more
I think that there are cases in which you cannot have a deployable SW at the end of each sprint. Consider the case of changing the operation system. Yes - you can take a flow at a time and get it to work. But before you deploy to production you would need to have feature parity to the current version. This is why you would need to work in branching for sometime.
I also like that the author acknowledg ...more
The book is easy to read, highly inspiring and well organised. It leads you from values through practices and principles to roles and more insightful chapters like Designing: The Value of Time - which was and still is so much needed in our industry. The mention about TPS stole my ...more
For everyone trying to make a shift in his/her software development approach mindset, is a a mandatory book. This book is the root, and since it is the second edition, it also explains how the seed idea came up and evolved since the initial iteration.
For me it consolidated the concepts spread around, and allowe ...more
For me, the most valuable thing was the catch the scientific ap ...more
Goodreads is hiring!
Learn more »