Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TECH ED] Watch the VSCode Debugger Video #166

Open
SallyMcGrath opened this issue Nov 24, 2023 · 0 comments
Open

[TECH ED] Watch the VSCode Debugger Video #166

SallyMcGrath opened this issue Nov 24, 2023 · 0 comments
Labels
📅 JS1 🏝️ Priority Stretch Do this once mandatory and key work is done 🦔 Size Tiny Less than 30 minutes 🎯 Topic Communication Reading, writing, speaking, and listening in English; expressing our ideas 🎯 Topic Requirements Interpreting requirements with precision and accuracy 🎯 Topic Testing It's important that software works and that people can use it 📅 Week 4

Comments

@SallyMcGrath
Copy link
Member

SallyMcGrath commented Nov 24, 2023

Link to the coursework

https://code.visualstudio.com/docs/introvideos/debugging

Why are we doing this?

🧰 We are building a toolkit to help us write great software. In our toolkit we are collecting skills with:

📝 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
Helps 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.

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. Watch the first four minutes of the video and then explore the VSCode Debugger on your machine.

Maximum time in hours

.5

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 VSCode.Talk me through the interface step by step. Provide a simple example of a Node script with a bug in it and walk me through finding the bug by setting breakpoints with the debugger. Don't tell me what the bug is. When I get stuck, answer my questions in CEFR B2 English meant for an adult professional speaking in a second language. When I ask for hints, give me useful pointers. Say okee dokee if you understand and begin your walkthrough.

Remember to use careful prompting when you don't understand, so you get real learning out of the exchange. Say things like:

The execution is paused and it shows me that i is undefined and this is undefined, but I don't understand why it says that. Can you explain this to me?

And remember you should always ask your friendly humans in Slack when you get really stuck. This coursework will be set again in later modules, so if it's beyond you right now, you'll pick it up later.

@SallyMcGrath SallyMcGrath added 🎯 Topic Communication Reading, writing, speaking, and listening in English; expressing our ideas 🎯 Topic Requirements Interpreting requirements with precision and accuracy 🎯 Topic Testing It's important that software works and that people can use it 🏕 Priority Mandatory This work is expected 📅 Week 1 🦔 Size Tiny Less than 30 minutes 📅 JS3 📅 JS1 📅 Week 4 🏝️ Priority Stretch Do this once mandatory and key work is done and removed 📅 JS3 📅 Week 1 🏕 Priority Mandatory This work is expected labels Nov 24, 2023
@SallyMcGrath SallyMcGrath moved this to 📋 Backlog in Module-JS1 Nov 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📅 JS1 🏝️ Priority Stretch Do this once mandatory and key work is done 🦔 Size Tiny Less than 30 minutes 🎯 Topic Communication Reading, writing, speaking, and listening in English; expressing our ideas 🎯 Topic Requirements Interpreting requirements with precision and accuracy 🎯 Topic Testing It's important that software works and that people can use it 📅 Week 4
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant