or
Sign in to turn on 1-Click ordering.
or
Amazon Prime Free Trial required. Sign up when you check out. Learn More
Sell Back Your Copy
For a $2.35 Gift Card
Trade in
More Buying Choices
Have one to sell? Sell yours here
Debugging by Thinking: A Multidisciplinary Approach (HP Technologies)
 
 
Tell the Publisher!
I'd like to read this book on Kindle

Don't have a Kindle? Get your Kindle here, or download a FREE Kindle Reading App.

Debugging by Thinking: A Multidisciplinary Approach (HP Technologies) [Paperback]

Robert Charles Metzger (Author)
4.7 out of 5 stars  See all reviews (6 customer reviews)

List Price: $76.95
Price: $48.80 & this item ships for FREE with Super Saver Shipping. Details
You Save: $28.15 (37%)
  Special Offers Available
o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
In Stock.
Ships from and sold by Amazon.com. Gift-wrap available.
Only 3 left in stock--order soon (more on the way).
Want it delivered Friday, February 3? Choose One-Day Shipping at checkout. Details
Textbook Student FREE Two-Day Shipping for students on millions of items. Learn more


Book Description

November 14, 2003 1555583075 978-1555583071 1
Debugging by Thinking: A Multi-Disciplinary Approach is the first book to apply the wisdom of six disciplines-logic, mathematics, psychology, safety analysis, computer science, and engineering-to the problem of debugging. It uses the methods of literary detectives such as Sherlock Holmes, the techniques of mathematical problem solving, the results of research into the cognitive psychology of human error, the root cause analyses of safety experts, the compiler analyses of computer science, and the processes of modern engineering to define a systematic approach to identifying and correcting software errors.

* Language Independent Methods: Examples are given in Java and C++
* Complete source code shows actual bugs, rather than contrived examples
* Examples are accessible with no more knowledge than a course in Data Structures and Algorithms requires
* A "thought process diary" shows how the author actually resolved the problems as they occurred

Special Offers and Product Promotions

  • Buy $50 in qualifying physical textbooks, get $5 in Amazon MP3 Credit. Here's how (restrictions apply)


Editorial Reviews

Book Description

Creative approach to improving the productivity of both novice and veteran programmers

From the Back Cover

"This comprehensive book on debugging techniques is a must-read for all novice programmers and provides a good value for advanced software developers. Debugging by Thinking describes various approaches to debugging and fills in a long-time gap in the software engineering library.
'To err is human'--software developers may know this fact better than other engineers. Debugging offers the only help for code errors, and this book analyses it as a mental discipline. After reading this book, your debugging will no longer be an ad hoc activity, and will become better organized and more efficient."- Dr. Piotr Findeisen, Systems & VLSI Technology Division, Hewlett-Packard Company

"Buy a copy of Debugging by Thinking for every programmer in your organization-it will help them to tackle debugging in a thoughtful, systematic, and effective way."-Richard Goldhor, VP of Engineering, Enounce, Inc.

Debugging by Thinking: A Multi-Disciplinary Approach uses the methods of literary detectives such as Sherlock Holmes, the techniques of mathematical problem solving, the results of research into the cognitive psychology of human error, the root cause analyses of safety experts, the compiler analyses of computer science, and the processes of modern engineering to define a systematic approach to identifying and correcting software errors.

Its unique features include
* Language Independent Methods: Examples are given in Java and C++
* Complete source code shows actual bugs, rather than contrived examples
* Examples are accessible with no more knowledge than a course in Data Structures and Algorithms requires
* A "thought process diary" shows how the author actually resolved the problems as they occurred

Product Details

  • Paperback: 600 pages
  • Publisher: Digital Press; 1 edition (November 14, 2003)
  • Language: English
  • ISBN-10: 1555583075
  • ISBN-13: 978-1555583071
  • Product Dimensions: 9.1 x 7.5 x 1.3 inches
  • Shipping Weight: 2.8 pounds (View shipping rates and policies)
  • Average Customer Review: 4.7 out of 5 stars  See all reviews (6 customer reviews)
  • Amazon Best Sellers Rank: #1,028,078 in Books (See Top 100 in Books)

 

Customer Reviews

6 Reviews
5 star:
 (4)
4 star:
 (2)
3 star:    (0)
2 star:    (0)
1 star:    (0)
 
 
 
 
 
Average Customer Review
4.7 out of 5 stars (6 customer reviews)
 
 
 
 
Share your thoughts with other customers:
Most Helpful Customer Reviews

5 of 5 people found the following review helpful:
4.0 out of 5 stars for new programmers, September 23, 2005
This review is from: Debugging by Thinking: A Multidisciplinary Approach (HP Technologies) (Paperback)
Often many programmers learn debugging by the sink or swim approach. Rarely in a computer science university education will much time be devoted to this crucial topic. But for the professional programmer, Metzger offers a systematic, disciplined approach. Examples are given in Java and C++. Actually, if you program elsewhere, you should still be able to easily follow the logic. He also shows how to effectively use a debugger to install breakpoints and step through code.

Experienced programmers should not need this text. There will be little new for you. But it is well suited for newcomers. An easier way to learn than purely through experience.
Help other customers find the most helpful reviews 
Was this review helpful to you? Yes No


1 of 2 people found the following review helpful:
4.0 out of 5 stars Interesting approach, not so good C++ code, September 27, 2006
This review is from: Debugging by Thinking: A Multidisciplinary Approach (HP Technologies) (Paperback)
The book lays out debugging strategies, heuristics, tactics, and approaches from the perspectives of detective, safety expert, psychologist, engineer, and computer scientist respectively. This is new! first! The text is an interesting read, and it helps the reader in his practice.

However, the case studies are a weak spot. The C++ code is not top notch, if pitted against the real, modern C++ according to Andrew Koenig ("Accelerated C++,") Scott Meyer ("Effective C++," "More Effective C++," "Effective STL,") Herb Sutter ("Exceptional C++," "More Exceptional C++," "C++ Coding Standards,") and Martin Fowler ("Refactoring.") In other words, the presented C++ code is rather like code written in 1993 than in 2003, when the book was published.
Help other customers find the most helpful reviews 
Was this review helpful to you? Yes No


3 of 8 people found the following review helpful:
5.0 out of 5 stars Excellent review of debugging techniques, June 24, 2004
By 
Dmitry Vostokov (Monkstown, Co. Dublin Ireland) - See all my reviews
Amazon Verified Purchase(What's this?)
This review is from: Debugging by Thinking: A Multidisciplinary Approach (HP Technologies) (Paperback)
Thanks for pointing out the sample chapter. I bought this book and found it very interesting. I was particularly impressed by Appendix B - Books about debugging. Also I have to add that one of the popular static analysis tools for C/C++/Java in EMEA is PRQA C/C++/J (Programming Research Ltd.)
Help other customers find the most helpful reviews 
Was this review helpful to you? Yes No

Share your thoughts with other customers: Create your own review
 
 
 
Most Recent Customer Reviews




Only search this product's reviews



Inside This Book (learn more)
First Sentence:
I don't believe that the story of a moth found in a relay of one of the first digital computers adequately explains why software defects are commonly referred to as bugs. Read the first page
Key Phrases - Statistically Improbable Phrases (SIPs): (learn more)
next debugging session, collateral software, moveup function, same undesired behavior, primary event line, debugging heuristics, heap integrity, offending optimization, additional testing strategy, next code sample shows, debugging infrastructure, following root causes, domestic drift, same test input, heap checking, been dereferenced, debugging tactics, slice strategy, subscript checking, preventing bugs, runtime procedures, refined tactics, greedy search strategy, ging information, horizontal pointers
Key Phrases - Capitalized Phrases (CAPs): (learn more)
Case Study, Lord Peter, Sherlock Holmes, Professor Solomon, Purpose Determine, Bounds Checker, Idiom Table, Henry Petroski, George Polya, Harriet Vane, Schoenfeld Schoenfeld, Applying Schoenfeld, Debugging Techniques, Purpose Identify, Sir Arthur Conan Doyle, Usage Under
New!
Concordance | Text Stats
Browse Sample Pages:
Front Cover | Table of Contents | First Pages | Index | Surprise Me!
Search Inside This Book:



Tags Customers Associate with This Product

 (What's this?)
Click on a tag to find related items, discussions, and people.
 

Your tags: Add your first tag
 

Sell a Digital Version of This Book in the Kindle Store

If you are a publisher or author and hold the digital rights to a book, you can sell a digital version of it in our Kindle Store. Learn more

Customer Discussions

This product's forum
Discussion Replies Latest Post
No discussions yet

Ask questions, Share opinions, Gain insight
Start a new discussion
Topic:
First post:
Prompts for sign-in
 


Active discussions in related forums
Search Customer Discussions
Search all Amazon discussions
   
Related forums





Look for Similar Items by Category


Look for Similar Items by Subject