java hosting


Title
Author
Publisher
ISBN
Reviewed by
Review text
Category

Your search returned 2 matching documents




Bug Patterns In Java
by Eric Allen


Apress
1 edition
October 2002
264 pages

Reviewed by Sujatha Rajagopalan, October 2002
  (7 of 10)


"Aim to write programs that are bug free". It is easier said than done.This book will be of special help to the Java developers and programmers who aim to develop robust programs. As developers and testers of Java applications multiply every day, it would come very handy to give them the symptoms and clues to detect a bug and make sure the code takes care of it smoothly. Several bugs go undetected in the real world due to the lack of time allotted for testing and debugging due to financial and other constraints. The author has thrown light at the importance of unit testing and debugging and explains a scientific approach to the same. He recommends extreme programming techniques to make the debugging process very simple yet sufficient.

The core portion of the book has a good structured approach to attach unique names to each bug and explains the symtoms and cure too. The initial part of the book concentrated on why debugging and testing was important. There was a big jump when the author goes into more technical details in Java codes and examples. Thats where the reader who has only a minimum knowledge in Java gets lost. This book cannot be recommended to developers in their learning phase. It focuses only on the audience who are Java literates who have been intensively coding in the same. It can be recommended for those Java programmers who want to become better Sherlock Holmes in detecting bugs in Java !

Discuss book in the Saloon More info at Amazon.com




Bug Patterns in Java
by Eric Allen


Apress
1 edition
October 2002
264 pages

Reviewed by Nathan Pruett, October 2003
  (8 of 10)


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 covered, the author also describes a methodical approach to tracking down bugs efficiently 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.

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.

Discuss book in the Saloon More info at Amazon.com

 
The Bunkhouse administrator is Ankit Garg.