forked from CodeYourFuture/Module-JS2
-
Notifications
You must be signed in to change notification settings - Fork 0
[TECH ED] Watch the VSCode Debugger Video #15
Copy link
Copy link
Open
Labels
🎯 Topic CommunicationReading, writing, speaking, and listening in English; expressing our ideasReading, writing, speaking, and listening in English; expressing our ideas🎯 Topic RequirementsInterpreting requirement with precision and accuracyInterpreting requirement with precision and accuracy🎯 Topic TestingIt is important that software works and people can use itIt is important that software works and people can use it🏝️ Priority StretchDo this once Mandatory and Key tasks are completedDo this once Mandatory and Key tasks are completed📅 JS2Worked assigned during JS2Worked assigned during JS2📅 Week 3Assigned during the week 3 of this moduleAssigned during the week 3 of this module🦔 Size TinyLess than 30minsLess than 30mins
Description
Activity
Metadata
Metadata
Assignees
Labels
🎯 Topic CommunicationReading, writing, speaking, and listening in English; expressing our ideasReading, writing, speaking, and listening in English; expressing our ideas🎯 Topic RequirementsInterpreting requirement with precision and accuracyInterpreting requirement with precision and accuracy🎯 Topic TestingIt is important that software works and people can use itIt is important that software works and people can use it🏝️ Priority StretchDo this once Mandatory and Key tasks are completedDo this once Mandatory and Key tasks are completed📅 JS2Worked assigned during JS2Worked assigned during JS2📅 Week 3Assigned during the week 3 of this moduleAssigned during the week 3 of this module🦔 Size TinyLess than 30minsLess than 30mins
From Module-JS2 created by SallyMcGrath: CodeYourFuture#115
From Module-JS3 created by SallyMcGrath: CodeYourFuture/Module-JS3#249
Link to the coursework
https://code.visualstudio.com/docs/introvideos/debugging
Why are we doing this?
For months now we have been building a toolkit to help us write great software. In our toolkit we have:
Specifications, like user stories, acceptance criteria, and Given/When/Then
Help us understand what to write and check we've written the right thing.
Tests, like unit tests and assertions
Help us break down our problems and check our solutions work even when we change things.
Asking questions
Help us formally reason through our problems and identify gaps in our mental models.
Playing computer
Helps us reason about code with a mental model.
Audits, like Lighthouse
Help us identify performance and quality improvements we can make to our code.
And now we can add debuggers to our toolkit.
Debuggers are tools that help us find and fix problems, or "bugs", in our JavaScript code. They let us step through our code line-by-line while it runs to see what is happening. This helps us find the place where our mental model of the code is different from our implementation. Your browser has a debugger and so does VSCode. You have used a similar program to "step through" code in your prep work.
Key reasons we use debuggers:
JavaScript debuggers give control over execution flow to methodically test and fix bugs. Watch the first four minutes of the video and then explore the VSCode Debugger on your machine.
Maximum time in hours
.25
How to get help
AI can help you here. Code along with AI so it has the context and ask it when you get stuck. Use this starting prompt:
Remember to use careful prompting when you don't understand, so you get real learning out of the exchange. Say things like:
And remember you should always ask your friendly humans in Slack when you get really stuck.