-
Notifications
You must be signed in to change notification settings - Fork 12
Description
Link to the coursework
https://developer.chrome.com/docs/devtools/javascript/
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:
- acceptance criteria, and Given/When/Then
- unit tests and assertions,
- Pythontutor,
- so on.
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.
Key reasons we use debuggers:
- See what's happening inside functions
- Check if variables have expected values
- Pause execution and step through slowly
- Find exactly where mistakes happen
JavaScript debuggers give control over execution flow to methodically test and fix bugs. Complete this tutorial (it's a 7 minute video plus tasks) to explore the Chrome Debugger.
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:
Act as a friendly, supportive, knowledgeable programming mentor. I am learning the debugger in Chrome Devtools. I'm doing this tutorial https://developer.chrome.com/docs/devtools/javascript/
Talk me through the tutorial step by step. Wait for me to confirm I've completed the step before going on to the next step. When I get stuck, answer my questions in CEFR B2 English meant for an adult professional speaking in a second language. Do not rephrase the tutorial text, just explain it when I ask you. Say okee dokee if you understand, and begin with step 1.