- Learn how to use a certain debugger religiously. Know its features from the inside out. For instance, I consider myself good enough to wield the Chrome Dev tools to the point that I can debug anything with it.
- Know different debugging techniques like the different ways to pause and inspect code. Know how to add breakpoints, break on exceptions, inject debugger statements in code and dynamically. How to read the stack traces and watch variables.
- Know your error messages. It's faster if you know how they're caused, rather than having to spend 5 mins on Google to know what caused it.
- If you're spearheading a project, choosing a good architecture could help. For instance, I have favored Flux over MVC because it pins down mutations to a single place - your stores. So if you can log actions and their payload, and the state of the store before and after mutation, then that could really help you debug the app.
- Know JavaScript. The language itself is your greatest tool.
- Learn how to use a certain debugger religiously. Know its features from the inside out. For instance, I consider myself good enough to wield the Chrome Dev tools to the point that I can debug anything with it.
- Know different debugging techniques like the different ways to pause and inspect code. Know how to add breakpoints, break on exceptions, inject debugger statements in code and dynamically. How to read the stack traces and watch variables.
- Know your error messages. It's faster if you know how they're caused, rather than having to spend 5 mins on Google to know what caused it.
- If you're spearheading a project, choosing a good architecture could help. For instance, I have favored Flux over MVC because it pins down mutations to a single place - your stores. So if you can log actions and their payload, and the state of the store before and after mutation, then that could really help you debug the app.
- Know JavaScript. The language itself is your greatest tool.