Even at our jobs people gloss over this essential skill. Unfortunately, this is a skill that Universities don’t really teach. Well… We spend 50% of our time chasing bugs according to this study, although I saw numbers ranging from 25% to 75%. Why do we need to go through a debugging tutorial? I already know programming and using a debugger isn’t exactly rocket science… The first part might seem a bit trivial since I’m assuming zero knowledge of debugging techniques but I plan to get in-depth with these posts as we move forward.īut you might be asking yourself, why even go through this?

The main goal in this series is to bring you up to speed so we can dig into the real interesting tutorials near the end. This might help if my instructions are unclear: Motivation

I also included a video tutorial highlighting the steps visually. However, these are a slightly different process so I’ll leave them out for now. In a future post I’d also like to also talk about browser debugging with Chrome DevTools and Firefox Web Developer Tools. We also move through languages/IDEs in our career and having a wider viewpoint is helpful. I think having all of them together is beneficial in providing the “big picture”. Normally people separate these tutorials based on IDE/Language. The same applies to most JVM languages like Scala etc. Notice that while I won’t cover TypeScript, everything discussed in the JavaScript tutorial is applicable to TypeScript too. These should cover most use cases you’ll run into and some things will seem duplicate/redundant so you can just skip to the applicable section if you feel you “got the gist”.

As we debug we’ll cover the techniques important for most developers. In this series I’ll walk you through the process of debugging applications and finding issues within them.

Download phpstorm debug javascript