[frontendmasters.com] Debugging and Fixing Common JavaScript Errors [2017, ENG]

Содержание

Table of Contents
Debugging JavaScript
Introduction
00:00:00 - 00:04:22
Introduction
Todd H. Gardner introduces his Debugging JavaScript course and agenda, which covers the process of finding bugs and the concepts to consider when working through the course of removing a bug.
Common JavaScript Quirks
00:05:48 - 00:15:50
Common JavaScript Quirks
After pulling a volunteer from the audience, Todd tests a student's knowledge to highlight the bizarre quirks in the JavaScript language.
Debugging Cycle
00:15:51 - 00:24:07
Debugging Cycle
Todd reviews a four stage of a debugging cycle to fix bugs: Identify, Isolate, Resolve, and Prevent.
Fixing Bugs
The getRANTr Application
00:24:08 - 00:28:00
The getRANTr Application
Todd introduces the demo application, getRANTr, that is used through the course.
Demo Application Review
00:29:54 - 00:32:57
Demo Application Review
After the students have installed the application as the learning tool, Todd shows how the application is built and which code sections students should focus their attention.
First Bug
Not Preventing the Default Behaviour
00:32:58 - 00:46:24
Not Preventing the Default Behaviour
Using Chrome DevTools, Todd demonstrates how to identify a bug by setting up persistent authoring to see changes immediately and save those changes to disk. - https://developers.google.com/web/tools/setup/setup-workflow
Challenge 1: Cannot Read Property
00:46:25 - 00:47:16
Challenge 1: Cannot Read Property
In this challenge, students need to identify and fix a "Cannot Read Property" bug.
Challenge 1: Solution
00:47:58 - 01:00:49
Challenge 1: Solution
Todd walks through the solution to Challenge 1 of function context by enabling async call stacks and blackboxing scripts in Chrome DevTools. - https://developers.google.com/web/tools/chrome-devtools/javascript/reference#call-stack
Second Bug
Challenge 2: Persisting Text
01:00:49 - 01:02:53
Challenge 2: Persisting Text
In this challenge, students identify and resolve a bug of persisting text.
Challenge 2: Solution
01:03:37 - 01:11:38
Challenge 2: Solution
Todd walks through the solution to Challenge 2 covering empty strings and falsy values.
Third Bug
Challenge 3: Server Reporting 400 Bad Request Errors
01:11:39 - 01:13:46
Challenge 3: Server Reporting 400 Bad Request Errors
In this challenge, students identify and resolve a user-form validation bug.
Questions 1
01:14:05 - 01:17:04
Questions 1
Todd answers questions from students about the first Challenge and how to remove extra event listeners added by frameworks. - https://developers.google.com/web/updates/2015/10/devtools-digest-reordering-tabs
Challenge 3: Solution
01:24:50 - 01:35:35
Challenge 3: Solution
Todd walks through the solution to Challenge 3 by using the Network Inspector, response previews, and JavaScript debugger and then Todd takes questions from students. - https://developers.google.com/web/tools/chrome-devtools/#network_panel
Fourth Bug
Challenge 4: One User, Many Errors
01:35:36 - 01:38:36
Challenge 4: One User, Many Errors
In this challenge, students attempt to determine why a user's data is not showing up.
Challenge 4: Solution
01:48:24 - 01:56:08
Challenge 4: Solution
Todd walks through the solution to Challenge 4 by using the Network Inspector, response previews, and JavaScript debugger.
JavaScript Quirks
Common JavaScript Quirks 2
02:00:03 - 00:00:00
Common JavaScript Quirks 2
Todd pulls another volunteer from the audience to review JavaScript quirks.
Fifth Bug
Unexpected High Memory Usage
02:09:19 - 02:25:31
Unexpected High Memory Usage
Demonstrating how to use Profiler and Timeline recordings in Chrome DevTools, Todd shows how to spot memory bugs in an application. - https://developers.google.com/web/tools/chrome-devtools/memory-problems/
Challenge 5: Memory Usage
02:25:32 - 02:26:00
Challenge 5: Memory Usage
In this challenge, students attempt to verify the memory leak is occurring with Chrome DevTools and pinpoint in the code where the leak is happening.
Challenge 5: Solution
02:36:00 - 02:51:07
Challenge 5: Solution
Todd walks through the solution to Challenge 5.
Sixth Bug
Slow Page Loads
02:51:08 - 02:56:42
Slow Page Loads
Using screenshots capability in Chrome DevTools, Todd shows how to illustrate a page rendering over time along with network activity.
Challenge 6: Impacts of Load Performance
02:56:43 - 02:57:30
Challenge 6: Impacts of Load Performance
In this challenge, students identify the biggest impact in load performance of the application using DevTools throttling and screenshots
Challenge 6: Solution
02:58:43 - 03:11:41
Challenge 6: Solution
Todd walks through the solution to Challenge 6 by looking for potential impacts in load performance of the application.
Seventh Bug
Third Party Error
03:11:42 - 03:14:21
Third Party Error
Inspecting a code error, Todd determines a bug is occurring due to a third party vendor's code.
Challenge 7: Uncontrolled Changes
03:14:21 - 03:16:45
Challenge 7: Uncontrolled Changes
In this challenge, students attempt to find out how to resolve a bug resulting from a third party vendor's code.
Challenge 7: Solution
03:27:03 - 03:35:47
Challenge 7: Solution
Todd walks through the solution to Challenge 7 by finding DOM inconsistency.
Eighth Bug
Network/Proxy Bug
03:35:48 - 03:53:47
Network/Proxy Bug
When a user has a bad experience with an application due to a third party script, Todd shows how to locate the error through load checking, simulating network speeds, and blocking scripts through a proxy. - https://www.charlesproxy.com/
Challenge 8: jQuery Fails to Load
03:53:48 - 03:54:36
Challenge 8: jQuery Fails to Load
In this challenge, students record an error has occurred and attempt to improve the user experience.
Challenge 8: Solution
03:55:32 - 04:01:41
Challenge 8: Solution
Todd walks through the solution to Challenge 8 by incorporating a failback when a third party code on a CDN fails to load.
Design for Debuggability
Questions 2
04:01:42 - 04:10:37
Questions 2
Todd answers questions from students about calling global objects, debugging bundled scripts, and setting cache timeouts.
Developing for a Hostile Environment
04:10:38 - 04:17:11
Developing for a Hostile Environment
Talking about monitoring for bugs within a web application, Todd reviews how to find bugs sooner and therefore cheaper.
Isolating Errors
04:17:12 - 04:26:44
Isolating Errors
Todd discusses when to refactor code and introduces the concept building a debug mode in an application. - - https://www.amazon.com/Refactoring-Improving-Design-Existing-Code/dp/0201485672 - https://saucelabs.com/
Resolving Bugs
04:26:45 - 04:31:29
Resolving Bugs
Todd extolls the virtue of setting up an update testing cycle when releasing code updates to lower the risk of change.
Preventing Bugs
04:31:30 - 04:38:44
Preventing Bugs
Thinking about how to prevent bugs from entering the code, Todd talks about introducing regression tests and updating processes as possible solutions realizing there is a cost associated with each.
Wrapping Up Debugging JavaScript
Wrapping Up
04:38:45 - 04:39:12
Wrapping Up
Todd reviews the course agenda and concludes the course.

Скриншоты