The Thoughtworks Anthology: Essays on Software Technology and Innovation (Pragmatic Programmers) [Paperback]

ThoughtWorks Inc. (Author)

Book Description

Publication Date: March 24, 2008 | Series: Pragmatic Programmers

ThoughtWorks is a well-known global consulting firm; ThoughtWorkers are leaders in areas of design, architecture, SOA, testing, and agile methodologies. This collection of essays brings together contributions from well-known ThoughtWorkers such as Martin Fowler, along with other authors you may not know yet. While ThoughtWorks is perhaps best known for their work in the Agile community, this anthology confronts issues throughout the software development life cycle. From technology issues that transcend methodology, to issues of realizing business value from applications, you'll find it here.

Editorial Reviews

About the Author

ThoughtWorks is a well-known global consulting firm; ThoughtWorkers are leaders in areas of design, architecture, SOA, testing, and agile methodologies.

Product Details

• Paperback: 248 pages
• Publisher: Pragmatic Bookshelf; 1 edition (March 24, 2008)
• Language: English
• ISBN-10: 193435614X
• ISBN-13: 978-1934356142
• Product Dimensions: 8.9 x 7.5 x 0.7 inches
• Shipping Weight: 1 pounds
• Average Customer Review: 3.8 out of 5 stars  See all reviews (5 customer reviews)

More About the Author

Discover books, learn about writers, read author blogs, and more.

Customer Reviews

Most Helpful Customer Reviews

6 of 7 people found the following review helpful:

4.0 out of 5 stars A good way to reflect on your profession, with a minor caveat..., May 26, 2008

By 

Thomas Duff "Duffbert" (Portland, OR United States) - See all my reviews
(VINE VOICE)    (TOP 500 REVIEWER)    (HALL OF FAME REVIEWER)    (REAL NAME)   

This review is from: The Thoughtworks Anthology: Essays on Software Technology and Innovation (Pragmatic Programmers) (Paperback)

I feel that every techie should take a step back once in a while and reflect on their profession. The ThoughtWorks Anthology: Essays on Software Technology and Innovation by ThoughtWorks, Inc. is one of those books that helps lead you down that path. While there are some good reads in here, the "level of resonance" will likely depend on your language of choice and development methodology...

Contents:
Solving the Business Software "Last Mile" by Rog Singham and Michael Robinson
One Lair and Twenty Ruby DSLs by Martin Fowler
The Lush Landscape of Languages by Rebecca J. Parsons
Polyglot Programming by Neal Ford
Object Calistentics by Jeff Bay
What Is an Iteration Manager Anyway? by Tiffany Lentz
Project Vital Signs by Stelios Pantazopoulos
Consumer-Driven Contracts: A Service Evolution Pattern by Ian Robinson
Domain Annotations by Erik Doernenburg
Refactoring Ant Build Files by Julian Simpson
Single-Click Software Release by Dave Farley
Agile vs. Waterfall Testing for Enterprise Web Apps by Kristan Vingrys
Pragmatic Performance Testing by James Bull

Based on the type of work that ThoughtWorks does and their development methodology, you'll understand and relate a lot more to the material if you're into things like agile development, Ruby, Ant, and other various open source software offerings. Granted, the argument could be made that *everyone* should be using those things, but the reality is that there are plenty of developers who don't or can't for various reasons. But once you get past that point, there's plenty of material here that should get you to think a bit... Lush Languages does a great job in turning the Java vs Ruby argument into one where you're considering multiple language options based on the problem domain. Polyglot Programming is also very insightful, as it addresses the use of multiple languages within a single project so that you can get the best of all possible worlds. If they are all running under the same JVM, there's few reasons not to take advantage of the various strengths. I also enjoyed the Object Calisthenics entry, as the exercises force you to rethink program design without resorting to techniques that can get out of control very quickly. Many of the other chapters are a bit more focused on topics that might or might not work for you if you're not already using that software/approach. You can always dig out one or two items that are not specific to the tool (as in development tool programming should fall under the same level of control and planning as production code), but you have to work a bit harder to get there.

If you're into the particular tools outlined here, by all means get the book and read it. If you're not at that spot for whatever reason, it's still worth reading. Just be prepared to work a little harder and/or realize that some of the chapters just won't do much for you.

3 of 4 people found the following review helpful:

4.0 out of 5 stars Enjoyable & Thoughtful Read, June 2, 2008

By 

Ambrose "Software Designer & Armchair Philoso... (Trenton, NJ, United States) - See all my reviews
(REAL NAME)   

This review is from: The Thoughtworks Anthology: Essays on Software Technology and Innovation (Pragmatic Programmers) (Paperback)

One nice thing about collections of short pieces is that you can work your way through them in any order and only read ones that look interesting without worrying about missing crucial information. That's how I read this book, and I enjoyed most of the selections I read. I thought that the one on OO coding was great as it had good concrete exercises to help folks go down that road.

Recommended.

2.0 out of 5 stars I was disapointed, November 10, 2010

By 

Marc Magrans De Abril - See all my reviews
(REAL NAME)   

This review is from: The Thoughtworks Anthology: Essays on Software Technology and Innovation (Pragmatic Programmers) (Paperback)

The book didn't fulfill my expectations. I was expecting either:
* Practical advice (e.g. Joel on Software)
* Design ideas (e.g. Beautiful code)
* or even personal and/or professional experience (e.g. Masterminds of programming, or the oral history of CS)

I was not able to recognize them. The only thing that is common to all the chapters is the advocacy and wording of Agile development. However, I didn't understood from the introduction, chapter titles, and previous reviews, that this was the aim of the book.

I do not recommend it.