A must have book for anyone writing programs.
— www.felgall.com
Overall, this book is going to be a huge win, and I think it’s a worthy successor to the Release It! reputation. Development managers and team leads should get a copy for the junior developers on their team as a Christmas gift, but only after the senior developers have read through it as well.
— blogs.tedneward.com
Excellent discussion of the strategy of debugging. Buy, it read it and kill bugs.
— i-programmer.info
Frankly, I wish this book would be read by a lot of developers
— www.jasonbock.net
With my many years of experience in supporting and debugging large existing enterprise systems, I have to say that Paul Butcher summarize and structure all the knowledge (and more) that I have, sometimes painfully, accumulated during this activity. This is therefore an excellent book that I will recommend to everybody that is involved in software development in general and maintenance activities specifically.
— blog.martinig.ch
I know that this book influenced the way I work now, and there aren’t many books I could say something like this about.
— devlicio.us
All in all, there is just a lot of tremendously valuable information in this book. And it’s only about 190 pages so it definitely won’t take you a long time to read it. I’ve frequently been amazed at the inability of developers to efficiently debug issues when they occur. And i’m not just talking about bad developers. I’ve seen plenty of good or even great developers having trouble with debugging efficiently. This book would definitely get them on the right track, with just a little bit effort.
— davybrion.com/blog
Understanding is everything: that is at the heart of Paul Butcher’s comprehensive study of the science and psychology of debugging.
— softtalkblog.wordpress.com
The book does a great (and truly pragmatic) job of covering all these aspects and addressing a wide range of topics related to debugging software.
— hamagudi.com
If you are too busy to read this delightful book in its entirety, then at least read the final chapter whilst mandating that your entire development team read “Debug It!” from cover to cover.
— javablog.co.uk
I would highly recommend Debug It! to any junior-level programmer who’s interested in developing a more disciplined approach to debugging. If you’re not a junior-level programmer but still feel like you waste a lot of time debugging, you will probably find this book helpful as well. It’s like having a mentor sitting there with you, teaching you how to take your debugging game to the next level.
— lylejohnson.name
It’s really good seeing these ideas in words because it’s quite easy to forget about the best way to approach problems in the heat of the moment and the approaches suggested by Paul certainly aren’t done everywhere in my experience.
— www.markhneedham.com
While I was familiar with many of the practices discussed in the book … I learned quite a few new things.
— starglider.blogspot.com
It does a great job of setting the scene for debugging and getting you into the right mind set, while also talking about the complications that can arise once the bug is found and squashed. It’s almost worth looking at for the anecdotes alone, to understand the lengths that you sometimes have to go to when trying to understand some truly bizarre defects.
— blog.jonmdickinson.com
This is a recommended read for anyone who works closely in the software industry, be it a developer, a tester or even a product manager.
— vidhujoshua.blogspot.com
) and I’ve just got around to uploading the photos:
The days of being able to get the engine out and back in again in between qualifying and the race are definitely behind me!
