Name Effects

Overview

In this lesson, students use Micro:bit block coding in MakeCode to create a simple program that displays their name and includes an effect. They will connect sequences of actions (code blocks) to what the Micro:bit does, building toward clear, testable programs.

Learning intentions

• Students will be able to build a MakeCode block program that shows their name on the Micro:bit.
• Students will be able to add at least one visual effect (e.g., scrolling, flashing, or an animation block) after the name displays.
• Students will be able to test and debug by comparing expected behavior to actual behavior.
• Students will be able to explain their program sequence using clear steps.

Success criteria

• I can find and use the correct display blocks (text/show/scroll) to present my name.
• I can add an effect so the Micro:bit changes visually in a noticeable way.
• I can run my program and confirm it matches my intended sequence.
• I can fix at least one issue using debugging strategies (change a block, re-run, re-check).

Curriculum links

• Engineering design through prototyping and testing (iterate based on results).
• Computational thinking: algorithmic thinking with step-by-step sequences and decomposition (show name, then effect).
• Mathematics connection for 6th grade learners: use of sequences/counting timing steps to support reasoning about ordered actions (aligns with interpreting and computing results in real contexts).
• Number line/absolute value and context reasoning can be referenced informally when students describe “distance” or “magnitude” of effects (optional teacher talk during debugging).

Lesson structure (45 minutes)

1. 0–5 min · Hook and demo

• Teacher quickly demonstrates a finished Micro:bit program: name scrolling across the LED matrix, followed by an effect.
• Students “predict the sequence” by writing two short steps: “First it…, then it…”.

2. 5–12 min · Direct teach: MakeCode blocks

• Teacher opens the MakeCode editor and models building blocks: choose Text/Show/Scroll blocks, then add an effect block and a pause if needed.
• Students follow along with a blank project, adding placeholders: scrolling text “NAME” and one effect (choose from the available effect blocks in MakeCode).

3. 12–20 min · Guided build: display your name

• Teacher circulates while students replace “NAME” with their real name, using the block that displays or scrolls text.
• Students test immediately after editing and adjust readability (e.g., spacing, speed, or using a pause).

4. 20–30 min · Add effects and timing

• Teacher shows how to add a second step: an effect that happens after the name (for example, flashing or another animation block), and how to use a pause block so the transition is clear.
• Students add at least one effect and at least one timing control (pause or delay block) and run the program twice to confirm consistency.

5. 30–38 min · Debugging sprint (pair work)

• Teacher gives a debugging checklist and models one common issue (text not showing or effect starting immediately).
• Students swap devices or screens: Partner A reads B’s block sequence and identifies one likely mismatch, then Partner B changes one block and re-runs to verify.

6. 38–45 min · Share-out and exit ticket

• Teacher calls on 2–3 students to share their sequence: “First my name scrolls, then my effect…”
• Students complete a quick exit ticket: (1) What blocks did you use for your name? (2) What effect did you add? (3) One change you made during debugging.

Resources

• Micro:bit(s) for each student or pairs
• MakeCode editor (Micro:bit target) with block coding view
• Printed or posted block screenshots (show/scroll text, effect/animation, pause/delay)
• Debugging checklist handout
• Timer for pacing (teacher visible)
• Student notebook or lab sheet for notes and exit ticket
• Optional: projector to display common block locations in MakeCode

Assessment

• Formative check during guided build: teacher confirms each student has name text blocks set and a program that runs.
• Formative pair debugging: teacher listens for accurate “expected vs. actual” statements and one successful fix.
• Exit ticket (3 questions) to verify effect usage, sequence description, and debugging reflection.

Differentiation

• Support:
• Provide a “starter code” block template already containing a scroll-text block and one effect block.
• Offer sentence frames: “My Micro:bit shows my name first because… Then it…”
• Use a printed block map so students can quickly find effect and pause blocks.
• Extension:
• Students who finish early can add a second effect after the first (two-step animation) or customize timing (more/less pause) to improve clarity.
• Encourage adding a conditional trigger if available (button press) while keeping the core “name then effect” requirement.
• EAL/SEN:
• Reduce language load by emphasizing visuals: students choose from a small list of effects rather than free-text descriptions.
• Allow extra time for copying the name; encourage uppercase formatting to ensure legibility.
• Grouping:
• Pair students strategically (one confident builder + one peer who needs more block support) to balance collaboration.

Micro:bit MakeCode focus (for the teacher)

• Students should primarily use blocks for:
• Displaying text (show/scroll name)
• Effects/animations (flashing/scrolling/other LED effects available in MakeCode)
• Sequencing and timing (pause/delay blocks between steps)