Tracing stacktrace is sometimes very boring. Especially your code is not above certain quality. If you’re an IntelliJ user, there are many many ways to trace your code like Exception Breakpoints, Field Watchpoints, Method Breakpoints and even JS breakpoints :) Anyways, today I needed to trace an exception in one of Eclipse project for work. I was gonna place an Exception Breakpoint, but then I remember that this is not IntelliJ. So a little investigation showed me that it is possible to place an Exception Breakpoint in Eclipse as well. Here is how I do it:

Couple weeks ago, I was waiting in the hospital line and luckily I had my MBP with me. I turned it on and tried Internet connection, but no luck. There was no free wireless access anywhere close :( Then I tried to connect through my iPhone 3G. This time I was lucky, it just worked. Here is how I did:

I’m sure every Java developer has had some hard times with NPEs (NullPointerException) since Java doesn’t really have a nice mechanism to avoid them :) Let’s recall something here: NPE is a run time exception and it occurs in the run time, therefore it means it is a design mistake, bad code quality or careless programming. Anyways, whatever the reason is, we all see NPEs all over our codes :) In this post, I want to cover this issue and give some tips from my experience so far.