EPORTFOLIO

Provide 3 to 5 best practices for debugging Java applications. Respond to at least two other learner posts.

1. 
   Ryan Bridglal said...
   10:51 pm - April 5th, 2009

   21 Mar 09 1:40 PM MST

   1.Let the debugger do the work for you. There are lots of free debuggers and compilers available. You can find one that helps you debug the program. With the Eclipse IDE, their debugger automatically locates the faulty code and provides suggestions to fix your code. With the NetBeans IDE, it will Identify the faulty code for you, but not provide automatic solutions. It provides suggestions to fix your code, but Eclipse will allow you to add code to help you resolve the situation.

   2.Get to know your debuggers and what they can do. Debugging is a powerful tool and each one does the job a little differently; even though they all do the same job. If you don’t know how to use it, you won’t get to far in programming.

   3.During debugging, after the debugger has identified the faulty code, you may not understand why the section is faulty. It’s best to read a few lines before or ahead to help you identify why the faulty code is not operation properly. If line 15 is faulty, maybe the method in line 5 is causing it.

   4. Another important thing when debugging is rewriting the faulty code. If you don’t rewrite

2. 
   Ryan Bridglal said...
   10:51 pm - April 5th, 2009

   Brooke Estabrook-Fishinghawk 22 Mar 09 9:50 AM MST

   Response to Ryan

   I agree 100%–why do the work if the debugger will do it for you?