Brain DeCoded with CodeX - Mission 1, Objective 2: Boot Up II
Mission 1 · Objective 2 Lesson Plan
Boot Up II
Students learn to use the built-in helpers in CodeSpace: the Toolbox, CodeTrek, and Hints.
⏱ 10-20 min
🎯 Grades 8-12+
💻 CodeSpace
🐍 Python
📋
Overview
Objective 2 continues the CodeSpace tour that started in Objective 1. Students learn about the three helpers built into the environment: the Toolbox, where they collect tools that explain CodeX and Python concepts, CodeTrek, a guide that walks through program code line by line, and Hints, which appear throughout the instructions with extra information.
These features are easy to skip past, so this objective is worth slowing down for. Students who use them get much more out of the rest of the pack.
🎯 Project Goal: Students will learn about the CodeSpace learning environment.
🎯
Learning Targets
- I can use helpful tools in CodeSpace.
💡
Key Concepts
- CodeSpace has a toolbox for collecting "tools". The tools give CodeX and Python information to help with programming.
- CodeSpace has a programming guide called "CodeTrek" that walks through program code.
- CodeSpace includes Hints throughout the instructions to give additional information and helpful hints for the project.
✅
Assessment Opportunities
- Click on a tool to add it to the toolbox.
- Click on CodeTrek and follow the instructions.
- Click on the Hints icon and read the hint.
- Exit ticket on when to use CodeTrek or Hints.
- Exit ticket on how to add a tool to the toolbox.
☑
Success Criteria
- Tool added to toolbox
- CodeTrek followed
- Hint read
📂
Digital Resources
🧰
Classroom Materials
- ▸Laptop/computer with Chrome browser
- ▸Student account in CodeSpace
- ▸Brain DeCoded with CodeX join code
- ▸No CodeX needed yet, the device is connected in Objective 3
🚀
Extensions & Cross-Curricular
ExtensionIf students didn't use the Hints or CodeTrek in Objective 1, have them go back and do so.
ExtensionStudents can keep a log of tools they click on.
ExtensionStudents can keep a journal of helpful hints they pick up along the way.
Lang ArtsStudents write a summary of debugging, which is a tool to click on.
Lang ArtsHave students explain to each other what the helpful tools are in CodeSpace, and when they should use each one.
🔢
Vocabulary
▾
Toolbox:a collection of CodeX and Python concepts that can aid in programming. A tool must be clicked on and added to the toolbox in order to be accessed.
Debugging:fixing problems, or bugs, in program code.
🐍
New Python Code
▾
from codex import *Added at the top of every program to access the codex library.
📐
Standards
▾
Computer Science - Grades 9-12
9-12.CS.1
📝
Preparing for the LessonSee Getting Started with CodeSpace for help with the steps below.
- Work through Objective 2 yourself so you know where the Toolbox, CodeTrek, and Hints icons live on the screen.
- Decide how you want students to record what they find, a log of tools or a journal of hints works well.
- No hardware or classroom materials are needed for this objective.
🧑🏫
Teacher Notes- The tools, CodeTrek, and Hints are embedded in CodeSpace as helpers to use throughout the mission pack. Students often overlook them or don't use them.
- Reinforce the need for using these tools to enhance the learning experience. It pays off in every objective that follows.
- Check in occasionally to see if students are clicking on the tools, reading the information in CodeTrek instead of just typing the code, and reading the hints.
- Extensions and cross-curricular projects are included to enhance the concepts in the objective. You can use the extensions to extend students' programming experience.
🗺️
Lesson Outline
🗣️Warm-up / Hook
Open with a quick discussion about getting unstuck.
- Ask: "When you get stuck on something new, what do you do first?"
- Ask: "What kind of help would actually be useful while you are writing code?"
Teaching tip: Keep this short. The whole objective runs 10-20 minutes and the point is to get students clicking on the tools themselves.
📖Introduce the Objective
Show the three helpers on the screen before students start working. Point to each one and say what it does.
- Toolbox: a collection of CodeX and Python concepts. A tool has to be clicked on to be added to the toolbox before it can be accessed later.
- CodeTrek: a guide that walks through the program code line by line and explains what each part does.
- Hints: extra information tucked throughout the instructions, opened with the Hints icon.
Teaching tip: Make the point that CodeTrek explains the code, so reading it beats copying the code straight into the editor.
💻Student Work Time
Students work through Objective 2 in CodeSpace.
- Students click on a tool to add it to the toolbox, then open the toolbox to find it.
- Students click on CodeTrek and follow the instructions through the program code.
- Students click the Hints icon and read the hint.
- Students complete the goal for the objective.
Teaching tip: Walk the room and watch for students who are typing code without opening CodeTrek. That is the habit to catch now, while the code is still short.
✏️Wrap-up & Review
Close with a short exit ticket. Two options that work well:
- When would you use CodeTrek, and when would you use a Hint?
- How do you add a tool to the toolbox?
Teaching tip: If students skipped the Hints or CodeTrek back in Objective 1, send them back to try them now. Starting a running log of tools or a journal of useful hints gives them something to build on for the rest of the pack.