Programming Books C Java PHP Python Learn more Browse Programming Books
Qty:1
  • List Price: $44.99
  • Save: $6.96 (15%)
Only 11 left in stock (more on the way).
Ships from and sold by Amazon.com.
Gift-wrap available.
Add to Cart
FREE Shipping on orders over $35.
Used: Good | Details
Sold by RentU
Condition: Used: Good
Comment: Fast shipping from Amazon! Qualifies for Prime Shipping and FREE standard shipping for orders over $35. Overnight, 2 day and International shipping available! Excellent Customer Service.. May not include supplements such as CD, access code or DVD.
Access codes and supplements are not guaranteed with used items.
Add to Cart
Have one to sell? Sell on Amazon
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See all 2 images

Making Software: What Really Works, and Why We Believe It Paperback – October 30, 2010

ISBN-13: 978-0596808327 ISBN-10: 0596808321 Edition: 1st

Buy New
Price: $38.03
43 New from $19.99 36 Used from $6.33
Rent from Amazon Price New from Used from
eTextbook
"Please retry"
$9.58
Paperback
"Please retry"
$38.03
$19.99 $6.33

Free%20Two-Day%20Shipping%20for%20College%20Students%20with%20Amazon%20Student



Frequently Bought Together

Making Software: What Really Works, and Why We Believe It + The Architecture Of Open Source Applications + The Architecture Of Open Source Applications, Volume Ii
Price for all three: $95.40

Buy the selected items together

NO_CONTENT_IN_FEATURE
Books for Pragmatic Programmers
Find resources for various programming needs, including agile teams, programming languages, and the life of a programmer, in the Pragmatic Bookshelf.

Product Details

  • Paperback: 624 pages
  • Publisher: O'Reilly Media; 1 edition (October 30, 2010)
  • Language: English
  • ISBN-10: 0596808321
  • ISBN-13: 978-0596808327
  • Product Dimensions: 9.1 x 6.9 x 1.3 inches
  • Shipping Weight: 1.8 pounds (View shipping rates and policies)
  • Average Customer Review: 3.7 out of 5 stars  See all reviews (11 customer reviews)
  • Amazon Best Sellers Rank: #280,135 in Books (See Top 100 in Books)

Editorial Reviews

About the Author

Andy Oram is an editor at O'Reilly Media, a highly respected book publisher and technology information provider. An employee of the company since 1992, Andy currently specializes in free software and open source technologies. His work for O'Reilly includes the first books ever published commercially in the United States on Linux, and the 2001 title Peer-to-Peer. His modest programming and system administration skills are mostly self-taught.

Greg Wilson has worked on high-performance scientific computing, data visualization, and computer security, and is currently project lead at Software Carpentry (http://software-carpentry.org). Greg has a Ph.D. in Computer Science from the University of Edinburgh, and has written and edited several technical and children's books, including "Beautiful Code" (O'Reilly, 2007).


More About the Author

Born and raised on Vancouver Island; studied engineering at Queen's University in Ontario, worked for a while, then went to Edinburgh for a Master's, some more work, and a PhD. Traveled while writing my first book on parallel programming; came to Toronto "for a couple of years" in 1994, and have never left. I've worked for big corporations, startups, and myself (prefer the small to the large), been a university professor (enjoyed the teaching more than the red tape), and am now project lead for Software Carpentry, a crash course on software development for scientists and engineers. You can find me online at http://third-bit.com (personal stuff) or http://software-carpentry.org (the course).

Related Media


Customer Reviews

3.7 out of 5 stars
Share your thoughts with other customers

Most Helpful Customer Reviews

42 of 44 people found the following review helpful By Michael C. Feathers on November 22, 2010
Format: Paperback Verified Purchase
I'm going to go on record and say that this is one of the most important books about software development that has been published in the last few years. It's easy for many of us in the industry to complain that software engineering research is years behind practice and that it is hard to construct experiments or perform studies which produce information that is relevant for practitioners, but fact is, there are many things we can learn from published studies.

The editors of this book do a great job of explaining what we can and can not expect from research. They also adopt a very pragmatic mindset, taking the point of view that appropriate practice is highly contextual. Research can provide us with evidence, but not necessarily conclusions.

Beyond the philosophical underpinnings, 'Making Software' outlines research results in a variety of areas. It gives you plenty to think about when considering various approaches on your team. The chapter 'How Effective is Modularization?' is worth the price of the book alone.

I recommend this book for anyone who wants to learn how to think rigorously about practice.
1 Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
26 of 27 people found the following review helpful By John Graham-Cumming on March 21, 2011
Format: Paperback
This is an important book and it covers a wide range of topics surrounding software engineering (comparing languages, whether TDD works, open source vs. proprietary, pair programming, metrics, learning to program, women in computer science and much, much more). But I can't give it a 5 star review because I wish it had been distilled down from a large collection of essays to a single book covering the conclusions and the data behind the conclusions.

It would be a 5 star if someone like Steve McConnell had taken the entire contents of the book and written a single coherent text from it. As it is the quality of writing and explanations varies a lot from article to article. For example, in some of the articles the authors decide to show us the code or the SQL statements used to extract data. I found this distracting (who cares how they pulled data from a database?) because I wanted to get to the meat of each piece. I suspect the book could be 1/2 to 2/3 the size it is today with a rewrite.

Despite my reservations this is a very worthwhile book. If you sit down to read it you'll likely find it hard going in places: it's dense and detailed. But that goes somewhat with the territory. This isn't a book about evangelizing the latest development fad, it's about hard data on what does and does not work in software engineering.

Refreshing, if a bit long.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
8 of 10 people found the following review helpful By Stephen Chapman on December 22, 2011
Format: Paperback
Thirty articles and thirty four different authors but you can't really tell that from reading the content as all of the material fits together extremely well.

The articles are divided up into two sections. The first covering general principles reads a lot like a fairly advanced university level textbook and it got really tempting for me to give up on the book a number of times while reading that section which would have been a real pity since the second section covering "Specific Topics in Software Engineering" is far easier to read and a lot more interesting as well.

There is plenty of material in the second section of the book that will help any programmer to improve the way that they write programs. A lot of the alternatives presented are beyond the control of the programmer though and so it is far more important that the managers in charge of programming departments be made aware of the information that this book provides.

While at least some of the information that the book presents should be obvious to any experienced programmer - some of the information may also be completely unexpected. The authors of the articles have done an excellent job though of specifying exactly how they obtained the data upon which their conclusions are based and so it should be reasonably easy to work out just how applicable each should be to any given situation.

I recommend that those without the background to fully understand the material in the first part of the book persevere with it as whatever part of it that you do manage to comprehend will aid in your understanding of what the extremely useful second part of the book actually means.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
Format: Kindle Edition Verified Purchase
This book is a collection of chapters on how to improve software development through empirically proven methods. In addition to good advice, the book teaches you how to conduct your own research, allowing you to customize to your own environment. It can be dry at times, but there is a wealth of material within the pages.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
7 of 11 people found the following review helpful By Daan on March 18, 2012
Format: Kindle Edition Verified Purchase
Note that this review is for the Kindle version! (Read on a Kindle Keyboard v3.3 using default settings.)

The kindle version of this book is very sloppy. We'll start at the beginning; the table of contents is needlessly indented. I consider indenting content that crosses several pages questionable in any occasion. This makes it even longer than it already is because chapter titles now often need two instead of one line. The book has links to the chapters, but counting that as an advantage in a digital version is like praising page numbers in a hard copy.

The book also offers links to references, but these sometimes span entire paragraphs or pages instead of just the author and year. This also happens to other links throughout the text.

Tables are not properly adjusted for the kindle, last characters of words are on new lines, columns headers are on the previous page, and sometimes columns are just cut off forcing you to decrease the font size. That shouldn't happen at the default font size. Chapter 12 includes an example of all of these.

Now that we're discussing chapter 12; the Clinical TDD Trial References are placed under a bibliography header on the next page instead of under that header (where they belong, as verified with a hard copy). This leaves a blank page. All other chapters have a single references header that avoids this problem.

The book is readable, but it's a very sloppy.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again

Customer Images

Most Recent Customer Reviews

Search

What Other Items Do Customers Buy After Viewing This Item?