Clica una miniatura per anar a Google Books.
Extreme Programming Explained: Embrace Change, 2nd Edition (The XP Series) (edició 2004)
de Kent Beck (Autor)
Informació de l'obra
Extreme Programming Explained: Embrace Change de Kent Beck
No hi ha cap discussió a Converses sobre aquesta obra.
XP is such a good set of patterns, Raising great development practices to a system that enhancing each other. This should be read by anyone taking part in a development team or tightly interacting with it. ( )
This book helped change the way that software development is generally practiced, from the leadership to the programmers, from the business to the design. It is important to note that this book has been delivered in two very different editions. The first edition in 1999 set the direction while the second edition in 2005 brought insight out of several years of experience in an updated text.
What’s so “extreme” about Extreme Programming? First, it advocates a practice called “pair programming” – programming in teams of two and sharing the burden of writing and debugging the code. Second, it advocates a heavy use of automated testing and writing those tests at the beginning of a new feature, not at the end. It also advocates the practice of continual integration – making many small deployments instead of one big deployment. This practice, 15 years after publication, is adhered to in most development shops.
What I like most about this book is that it flattens the landscape. Instead of having hierarchies and bureaucracies, it brings responsibility to everyone on the team. This is especially true in my industry, medical research. It’s in touch with the evolving dynamics of the workplace. Careers should not be a race to the top but a continual development of skill. Lean production techniques, concepts of continual improvement, and shared responsibility are all consulted in suggesting how to handle the business of software. The purported results are substantially reduced software defects (i.e., improved quality) and slightly reduced development time (i.e., reduced cost).
While these ideas were cutting-edge in 1999 (and still not widely practiced in 2005), they are expected in most software shops in 2020. Thus, this book is to be consulted as a vestige of history rather than a set of new ideas to implement. It’s still interesting, relevant, and inspirational because of the revolution it sparked. I read this book as a way to think through the practice of test-driven development. It helped me with that practice and continues to catalogue what good software development consists of. Interestingly, these skills have developed into Agile practices and more recent DevOps trends. Writing about these topics should now be consulted for state-of-the-art.
Very timely in the early 2000s. Fights the bureaucracy of the methodologies of the "3 amigos" - Booch, Rumbaugh and Jacobsen - which became the Unified Process (RUP).
If you want to learn the principles of XP, this is THE book. If you want to learn the practice of XP, there are better alternatives.
The ideas and motivation of XP are explained clearly and concisely. It's a short read, but fairly convincing. However, if you learn better from examples, this book does not have enough real world stories to really see XP in action.
The book is full of great quotes:
XP is a lightweight methodology for small-to-medium-sized teams developing software in the face of vague or rapidly changing requirements.
Everything in software changes. The requirements change. The design changes. The business changes. The technology changes. The team changes. The team members change. The problem isn't change, because change is going to happen; the problem, rather, is our inability to cope with change.
No book of gardening, however complete, makes you a gardener. First you have to garden, then join the community of gardeners, then teach others to garden. Then you are a garden
As Will Rogers said, “It ain't what you don't know that gets you in trouble. It's what you know that ain't so.”
If members of a team don't care about each other and what they are doing, XP won't work. If members of a team don't care about a project, nothing can save it.
In software development, “perfect” is a verb, not an adjective.
Quality isn't a purely economic factor. People need to do work they are proud of.
Automatically build the whole system and run all of the tests in ten minutes. A build that takes longer than ten minutes will be used much less often, missing the opportunity for feedback. A shorter build doesn't give you time to drink your coffee.
Put new software into production every night. Any gap between what is on a programmer's desk and what is in production is a risk. A programmer out of sync with the deployed software risks making decisions without getting accurate feedback about those decisions.
Silence is the sound of risk piling up.
He picked a powerful metaphor for his teaching, Scientific Management. When picking descriptive names, it helps to pick a name whose opposite is unappealing. Who could possibly be for “unscientific” management?
Having a separate quality department sends the message that quality is exactly as important to engineering as marketing or sales. No one in engineering is responsible for quality.
This is an odd book. It is propaganda for a now popular software development method, but its strongest arguments have nothing to do with productivity or cost savings. Instead, they appeal to the personal integrity of software professionals: they are about identifying the values one upholds and, if they match those of Beck's Extreme Programming, to use his practices as a means to satisfying them.
The second edition of this book is more mature than the first. Beck doesn't talk as much about "cranking the dials up to 10" and he is far less dogmatic, and far more reflexive, about the right way to develop software. At some points (in particular with some of the corollary practices he proposes) the arguments are thin and too reliant on anecdotal evidence. But still, this is a great book, and I welcome the emphasis on values, on the humanity of software development, on communication, on professional commitment to work well done. It is refreshing to read not only that developers are not cogs in a machine, but that this is the essential insight of responsible software practice and needs to be taken to its extreme consequences.
Es mostren 1-5 de 9 (següent | mostra-les totes)
Referències a aquesta obra en fonts externes.
Wikipedia en anglès (8)
"Extreme Programming (XP) was conceived and developed to address the specific needs of software development conducted by small teams in the face of vague and changing requirements. This new lightweight methodology challenges many conventional tenets, including the long-held assumption that the cost of changing a piece of software necessarily rises dramatically over the course of time. XP recognizes that projects have to work to achieve this reduction in cost and exploit the savings once they have been earned." "You may love XP or you may hate it, but Extreme Programming Explained will force you to take a fresh look at how you develop software."--Jacket.
No s'han trobat descripcions de biblioteca.
Amazon Kindle (0 edicions)
Audible (0 edicions)
CD Audiobook (0 edicions)
Project Gutenberg (0 edicions)
Google Books — S'està carregant…
Classificació Decimal de Dewey (DDC)005.1Information Computing and Information Computer programming, programs, data, security Programming
LCC (Clas. Bibl. Congrés EUA)
Fes-te Autor del LibraryThing.