Picture of author.
17+ teosta 2,394 jäsentä 23 arvostelua 4 Favorited

Tietoja tekijästä

Sisältää nimet: Kent Beck, Кент Бек

Tekijän teokset

Associated Works

Refactoring: Improving the Design of Existing Code (1999) — Avustaja — 1,814 kappaletta
User Stories Applied: For Agile Software Development (2004) — Esipuhe, eräät painokset548 kappaletta

Merkitty avainsanalla

Yleistieto

Syntymäaika
1961
Sukupuoli
male
Kansalaisuus
USA
Koulutus
University of Oregon (M. S.)
Organisaatiot
"Three rivers institute"

Jäseniä

Kirja-arvosteluja

Despite the terrible name, a mind opening title for programmers and managers alike. It will take time to apply everything this book suggests, but I'm a convert already.
 
Merkitty asiattomaksi
zeh | 9 muuta kirja-arvostelua | Jun 3, 2023 |
This is one of those books that I would have rated more highly a few years ago. TDD is not a particularly complicated concept and, these days, it's not particularly new either. Thus, the explanations I've come across online[1] and the one book I've read on the topic[2] have been quite sufficient exposure, making reading another book on the topic superfluous.

That said, Beck's book was, in my opinion, better than Test-Driven Development: A Practical Guide by David Astels. Astels' book is not bad, but it's over 500 pages long, and TDD just isn't really that complicated. Beck's book, at ~200 pages of fairly spacious typesetting, is much more proportional to the complexity of the topic (websites are even shorter, but I prefer to read books, especially when they are available from the library at work).

In short, if you are interested in learning about TDD -- and I think it's an approach all programmer should learn about and apply judiciously but not religiously -- I recommend reading about it on the internet and then, if you're a book person or want to see a more extended example, read Beck's book.

[1] http://en.wikipedia.org/wiki/Test-driven_development and http://www.agiledata.org/essays/tdd.html
[2] test-driven development: A Practical Guide by David Astels
… (lisätietoja)
 
Merkitty asiattomaksi
eri_kars | 8 muuta kirja-arvostelua | Jul 10, 2022 |
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.
 
Merkitty asiattomaksi
paven | 9 muuta kirja-arvostelua | Jan 26, 2021 |
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.
… (lisätietoja)
 
Merkitty asiattomaksi
scottjpearson | 9 muuta kirja-arvostelua | Feb 5, 2020 |

You May Also Like

Associated Authors

Tilastot

Teokset
17
Also by
2
Jäseniä
2,394
Suosituimmuussija
#10,721
Arvio (tähdet)
4.1
Kirja-arvosteluja
23
ISBN:t
41
Kielet
12
Kuinka monen suosikki
4

Taulukot ja kaaviot