[ PRACTICAL SCHOOL GUIDE ]
Choosing models for coding classes
Evaluate explanation, debugging, and instructional restraint.
The idea
Evaluate explanation, debugging, and instructional restraint.
Classroom example
Give a model a failing function and ask for a clue before code. Check whether it explains the defect and lets the student make the repair.
Try this next
Use this checklist for choosing models for coding classes.
- Test several course levels
- Include insecure and ambiguous code
- Decide when full solutions are allowed
Review the explanation behind the code
For a programming lesson, a useful response can identify an error and ask the student to reason about a fix. A complete working program may defeat the lesson if the objective is understanding control flow or decomposition.
Try it with your school
- Include a small failing example.
- Ask for a hint before a replacement solution.
- Run the proposed change in a safe test environment.
- Ask the learner to explain why the test passes.
Review the result
Evaluate correctness and instructional behavior separately. Code that runs is not proof that the student understands it, and generated code still needs review.