Advanced JavaScript


Debugging takes time and brainpower even for the very best programmers, and it can be one of the most frustrating parts of the job. However, no one can argue, debugging is an essential skill for any developer. This blog series introduces and explains some strategies that can be used to diagnose and fix bugs, some are specific to JavaScript while others can be applied to any programming language.


Part One

In this first part, you will learn how to validate Your assumptions, how to use binary search effectively, and all about the debugger statement.

Part Two

This post describes two important techniques that can be applied to debugging any programming language: bottom-up and top-down debugging.

Part Three

The last part of the series is focused on how teams that use Agile can help their developers and QAs debug JavaScript effectively.

About the Author

Zach Gardner

Zach Gardner is a Keyhole Software Senior Consultant with more than a decade of development experience. Zach has led numerous initiatives to modernize technologies and processes with real-world experience as an educator, architect, technical lead, developer, and mentor. He primarily lives in Microsoft Azure, leveraging modern architectural approaches to enable hybrid app modernization that meets business needs at an exceptional cadence. He also mentors new developers and provides architectural input to complement the existing talent of clients.

Additional Resources

The Keyhole development blog has published another post on this subject, Time-Oriented Debugging. The post was written by the same author as the series above and offers more valuable insight into this topic.

For more articles about JavaScript, take a look at our other blogs regarding the subject.