Inference | Guided Practice
Adult learners practice making and evaluating inferences from incomplete information in computer science contexts. Students use logs, code snippets, and data patterns to distinguish evidence-based conclusions from assumptions, improve debugging decisions, and justify their reasoning verbally and in writing.
| Term | Definition |
|---|---|
| Inference | A conclusion drawn from evidence and reasoning rather than direct observation. |
| Assumption | A belief accepted without sufficient evidence; in computing, this can lead to errors. |
| Evidence | Observable data such as code behavior, logs, outputs, or error messages used to support a conclusion. |
| Hypothesis | A testable explanation that can be checked against evidence. |
| Debugging | The process of finding and fixing errors in code or systems. |
| Pattern | A repeated or consistent feature in data, output, or behavior that may suggest a cause. |
| Trace | Step-by-step information showing how a program or system executed. |
| Confidence | How strongly evidence supports a conclusion. |
Display a short error message, program output, or log snippet. Ask: What can we know for sure? What can we infer? Record student responses in two columns: evidence and inference.
Individually write observations, then share one evidence-based statement and one inference with a partner.
Model a think-aloud using a sample debugging scenario. Show how to move from evidence to a cautious inference, and contrast it with an unsupported assumption.
Follow the model, highlight evidence in the example, and identify where the reasoning becomes an inference.
Provide a code snippet with a subtle bug and corresponding output/logs. Guide students through questions: What happened? What evidence supports that? What is the most likely inference? What else could explain it?
Work in pairs to annotate the snippet and write a short inference statement with evidence.
Give small groups 2-3 short scenarios involving system logs, failed tests, or unusual program behavior. Circulate, prompt for evidence, and press for alternative explanations.
Collaboratively complete each scenario by identifying evidence, making an inference, and rating confidence as high/medium/low.
Invite groups to share one scenario. Ask peers to challenge or refine the inference by naming missing evidence or alternative causes.
Explain reasoning, compare inferences, and revise one response based on peer feedback.
Assign a brief individual prompt: Given a new log or output sample, write one inference, the evidence supporting it, and one question that would help confirm it.
Complete the prompt independently and submit for assessment.
Revisit the two-column evidence/inference chart and ask students to name one key takeaway about avoiding assumptions in computer science. Emphasize that strong inference is specific, evidence-based, and open to revision when new data appears.
Formative assessment is embedded throughout guided practice and discussion. The independent short response serves as the summative check for the lesson: students must identify evidence, make a defensible inference, and note one follow-up question or test. Use a simple rubric for evidence accuracy, reasoning clarity, and appropriate vocabulary.
Find a real or simulated computer science example at work, online, or in a provided handout where a conclusion is made from logs, code, or data. Write a one-paragraph analysis identifying the evidence, the inference, and whether the inference is strong or weak. Include one alternative explanation or question for further testing.