Detecting app bugs play a crucial role in fixing the performance of different applications before or after releasing them in the market.

The debugger watch area is a powerful tool, it's worthy of two lessons in the course. If you don't know about Object Marking you need to see this!

Learn about tracepoints (AKA logpoints) how exception breakpoints don't have to suck, watchpoints, filters & why method breakpoints are problematic.

Java 8 streams improved code readability they also provide great debugging opportunities. There are amazing tools for inspecting collections & arrays.

Stop digging through variables in the watch to find nuggets of gold, or rerunning the expression evaluation. Use entity renderers instead.

Track thread race conditions, figure out deadlocks, and understand the flow of asynchronous applications (even in custom code) using the debugger.

This isn't just about memory leaks. Understanding how RAM is used and its content provides insight into the app you can't get in any other way!

Debugging over the network using a protocol like JDWP isn't hard. However, there are risks that aren't immediately intuitive and some subtle solutions

16 missing features in the VS code debugger that are available in IntelliJ/IDEA. Are they worth switching your main IDE? Detailed lists and videos.

Applications fail, that's inevitable. All the testing, QA, CI and defensive programming can make this a rare occurrence, but can't eliminate failure.