Coding Tutoring

Placing blocks in sequence without checking the order

Commands execute in the order they appear. If a sprite is told to hide before it moves, the movement will not be visible. Tutors can ask students to predict what happens at each step, run the code, and adjust the sequence when the observed behavior does not match the goal.

Confusing the number of repetitions with the repeated action

A repeat block controls how many times an action occurs, not what the action does. Students may set a repeat count without identifying which commands belong inside the loop. Tutors can show the difference between repeating move forward three times and moving forward by three steps once.

Using a conditional without understanding the test

An if-then block checks whether a condition is true before running the code inside. Students may place commands in the conditional section without explaining what is being tested. Tutors can ask what happens when the condition is true, what happens when it is false, and which outcome the current code produces.

Treating a variable as a fixed label

A variable holds a value that can change during the program. Setting score to zero at the start and changing score by one when an event occurs are two different commands. Tutors can trace how the variable updates and ask students to explain its value at a specific point in the code.

Typing syntax from memory without checking each required element

In Python 3, printing a string uses a function call such as print("Hello"). Unmatched quotes or parentheses can cause a syntax error, and an indented function body is required after a function definition. Spaces around an assignment's equals sign improve readability but are not required syntax: count=0 and count = 0 both work.

Show what each command does before combining them

Tutors can isolate one block or line, run it, and observe the result. Students can then add the next command and check whether the program behaves as expected. This makes debugging easier because each addition has a clear purpose and a testable outcome.

1. Identify the goal for the program or sprite.
2. Add one command and run the code to observe its effect.
3. Add the next command and check whether the sequence produces the intended result.
4. Adjust the order, parameters, or structure when the behavior does not match the goal.

Connect a loop to the pattern it replaces

Students can write move forward, move forward, move forward, then replace the repetition with a repeat-three-times block containing one move-forward command. Tutors can ask what changes when the repeat count increases and what stays the same, helping students distinguish the loop's control from the action it repeats.

Trace a variable's value through the program

Start with a variable set to zero. Each time a condition is met, the variable changes by one. Tutors can ask students to state the variable's value after each update and explain what triggers the change. This connects the variable's role to the program's logic rather than treating it as a display label.

From repeated commands to a loop

Sequence four move-forward blocks to navigate a grid. Then replace them with a repeat-four-times block containing one move-forward command. Run both versions and confirm they produce the same result. Students can explain what the number four controls and what happens inside the loop.

From a variable's starting value to its updated state

Set a variable called count to zero. Add a command that changes count by one when a sprite is clicked. Click the sprite three times and check the variable display. Students can explain why the value is now three and predict what happens after two more clicks.