Bug Patterns In Java (Paperback)

by Eric Allen (Author)
Key Phrases: double descent, impostor type, orphaned thread, Fictitious Implementation, Liar View, Run-On Initializer (more...)

Editorial Reviews

Product Description
<p><i>Bug Patterns in Java</i> presents a methodology for diagnosing and debugging computer programs. The act of debugging will be presented as an ideal application of the scientific method. Skill in this area is entirely independent of other programming skills, such as designing for extensibility and reuse. Nevertheless, it is seldom taught explicitly. Eric Allen lays out a theory of debugging, and how it relates to the rest of the development cycle. In particular, he stresses the critical role of unit testing in effective debugging. At the same time, he argues that testing and debugging, while often conflated, are properly considered to be distinct tasks.</p>

<p>Upon laying this groundwork, Allen then discusses various "bug patterns" (recurring relationships between signaled errors and underlying bugs in a program) that occur frequently in computer programs. For each pattern, the book discusses how to identify them, how to treat them, and how to prevent them.</p>

About the Author
Eric Allen has a bachelor’s degree in computer science and mathematics from Cornell University, and is a Ph.D. candidate in the Java programming languages team at Rice University. His research concerns the development of semantic models and static analysis tools for the Java language, both at the source and bytecode levels. Currently, Eric is constructing a compiler for the NextGen programming language, an extension of the Java language with added language features. He has also moderated the Java Beginner discussion forum at JavaWorld and is a project manager of DrJava, an open source Java IDE designed for beginners.

Product Details

• Paperback: 264 pages
• Publisher: Apress (October 4, 2002)
• Language: English
• ISBN-10: 1590590619
• ISBN-13: 978-1590590614
• Product Dimensions: 9.1 x 7.4 x 0.3 inches
• Shipping Weight: 8.8 ounces
• Average Customer Review: 4.3 out of 5 stars See all reviews (6 customer reviews)
• Amazon.com Sales Rank: #1,159,998 in Books (See Bestsellers in Books)

  Popular in this category: (What's this?)

  #50 in

  Books > Computers & Internet > Programming > Languages & Tools > Debugging

Customer Reviews

Most Helpful Customer Reviews

4 of 4 people found the following review helpful:

5.0 out of 5 stars Great Guide to Debugging, October 2, 2003

By	"ntpruett" (Eagan, MN United States) - See all my reviews

Bugs. All code has them to one degree or another and they always seem to take twice as long to fix as the original code took to write. This book boils thirteen of the most common bugs down to their root causes and formulates them as 'bug patterns'. Each bug pattern describes how to identify the bug by the symptoms it exhibits, why the bug is occurring, and gives one or more suggestions to fix it and prevent it from occurring again.
If the bug you are searching for isn't among one of the thirteen bug patterns covered, the author also covers a methodical approach to tracking down bugs effieciently and quickly. Suggestions on how to prevent bugs from occurring in various stages of the development cycle are also presented, which are helpful even if you aren't currently searching for a bug in your code. Most of the suggestions are based on the XP development model, but the practices that are important are pointed out so they can be incorporated into any other style of development.
Even though debugging doesn't sound like a fun topic, the author has a very readable style and is able to get you excited about preventing and fixing bugs. The chapters have been very well thought out and the book is broken into topics very well. You can read a chapter in about ten minutes or less and feel like you have a good grasp of the topic covered.
This is a great book to partner with a 'best coding practices' type of book, like 'Practical Java' or 'Effective Java'. Those books are really good at describing how Java should be coded. This book gives examples of why those practices should be followed, and how to quickly get back on track when they aren't and something goes wrong.

2 of 2 people found the following review helpful:

5.0 out of 5 stars Valuable Resource, April 28, 2003

By	C. M. Lowry (Columbia JUG, Columbia, SC USA) - See all my reviews

Time is a very valuable resource on every project, and this book can help conserve that resource. The first six chapters of the book present defect management within the larger concept of Agile development methods. Chapters 7-20 detail various bug patterns with symptoms, causes, cures, and preventions. The remainder of the book provides some nice resources like a diagnostic checklist, a glossary, a reference list, and an index.

I recognized some of the patterns from the author's column on developerWorks, but the book does a solid of pulling them together to present debugging as a rather orderly and scientific process. The author relies on his real project experience with the DrJava project to illustrate his examples. Various tables are available to link concepts with potential bug patterns or problems to a bug pattern that could be related.

The patterns are explained and depicted with code with each chapter having a summary of the concepts at the end. Tips and variations on the patterns are sprinkled in the text. I found the glossary of particularly helpful. The text is easy to read and the examples are clearly explained. This book and "Bitter Java" may have a good "ROI" as required reading for Java developers.

2 of 2 people found the following review helpful:

5.0 out of 5 stars An excellent reference, very well organized, March 28, 2003

By	Janine M. Joseph (Buffalo, NY United States) - See all my reviews

A great Java resource for programmers of widely varying experience levels. Author found the perfect balance between theory and practical application. There is a wealth of useful information in the chapters devoted to detailed descriptions of the symptoms and cures for the most common and/or most troublesome Java bugs. The book is organized in a very friendly way, making it an excellent reference. I plan on keeping this book very handy.