Reading Comprehension | Mini Lesson
Students learn and practice strategies for reading dense technical documentation, code comments, API references, and problem prompts in order to extract meaning, identify requirements, and translate text into working code decisions. This mini lesson emphasizes active reading, annotation, and evidence-based interpretation in coding contexts.
| Term | Definition |
|---|---|
| Technical text | Writing that explains how a system, tool, or code works, often using precise language and specialized terms. |
| Constraint | A limitation or rule that must be followed when solving a programming task. |
| Inference | A conclusion drawn from clues in the text that is not stated directly. |
| Annotation | Marks, notes, or highlights added to a text to identify important information. |
| Specification | A statement of what a program, function, or system must do. |
| Evidence | A quoted or paraphrased detail from the text used to support an interpretation or decision. |
Display a short, confusing coding prompt. Ask students to identify what the task is asking, what is unclear, and what details seem most important.
Individually jot quick responses, then share one observation with a partner.
Model a think-aloud using a technical prompt or API snippet. Demonstrate a three-step routine: identify the task, mark constraints, and list unknowns/questions.
Follow along, annotate the sample, and label at least one requirement, one constraint, and one inference.
Provide a new prompt. Guide students through chunking the text sentence by sentence. Ask targeted questions about verbs, conditions, edge cases, and output expectations.
Work in pairs to annotate the prompt and create a short checklist of what the solution must do.
Ask pairs to turn their annotations into a brief pseudocode outline or implementation plan. Circulate and prompt students to justify choices using text evidence.
Draft a plan, compare with a partner, and revise if the plan misses a requirement or constraint.
Present a slightly ambiguous extension or altered prompt. Ask students to identify at least one likely ambiguity and propose a clarifying question or assumption.
Individually write a response, then discuss which interpretation is safest and why.
Distribute an exit ticket with a short technical paragraph and three prompts: summarize the task, list two constraints, and explain one implementation choice with evidence.
Complete the exit ticket independently and submit before leaving.
Bring the class back together to name the most useful reading strategy from the lesson. Emphasize that strong coding depends on precise reading, careful annotation, and evidence-based decisions before writing code.
Students complete an exit ticket that demonstrates comprehension of a technical text by summarizing the task, identifying constraints, and supporting an implementation decision with evidence from the text. Responses are scored for accuracy, completeness, and clarity.
Choose a short documentation page, function description, or coding challenge prompt. Annotate it using the class strategy, then write a 1-paragraph summary of the task, two constraints, and one question you would ask before coding.