Stomp out bugs and clean up JavaScript apps! In this course, Todd Gardner (Co-founder of TrackJS), walks through common JavaScript bugs and how to isolate and fix the source of the problems. By coding along, you'll learn the four stages of a debugging cycle needed to fix bugs. Use Chrome Dev Tools, debugger, network profile and more to fix memory leaks, performance problems, network failures and more! This course is for any JavaScript developer that builds, maintains, or tests an application that uses JavaScript. With the knowledge you gain, you’ll be armed to find and squash those bugs faster and for good!
Overview
Syllabus
- Introduction
- Common JavaScript Quirks
- Debugging Cycle
- The getRANTr Application
- Demo Application Review
- Not Preventing the Default Behaviour
- Challenge 1: Cannot Read Property
- Challenge 1: Solution
- Challenge 2: Persisting Text
- Challenge 2: Solution
- Challenge 3: Server Reporting 400 Bad Request Errors
- Questions 1
- Challenge 3: Solution
- Challenge 4: One User, Many Errors
- Challenge 4: Solution
- Common JavaScript Quirks 2
- Unexpected High Memory Usage
- Challenge 5: Memory Usage
- Challenge 5: Solution
- Slow Page Loads
- Challenge 6: Impacts of Load Performance
- Challenge 6: Solution
- Third Party Error
- Challenge 7: Uncontrolled Changes
- Challenge 7: Solution
- Network/Proxy Bug
- Challenge 8: jQuery Fails to Load
- Challenge 8: Solution
- Questions 2
- Developing for a Hostile Environment
- Isolating Errors
- Resolving Bugs
- Preventing Bugs
- Wrapping Up
Taught by
Todd Gardner
