Repair: Read, Check and Ask for Help

This lesson complements the study-systems module. It practises interpreting technical instructions and producing evidence when stuck; it does not add another habit-tracking system.

Turn words into examples

Given “Accept whole minutes from 1 through 240 inclusive,” underline the noun, type, boundaries and qualifier. “Whole” excludes 2.5; “inclusive” accepts both 1 and 240. Predict an ordinary case, each endpoint, and a case immediately outside each endpoint before coding. If instructions do not specify blank input, ask or document an assumption rather than silently deciding it means zero.

For a different contract, “Accept between 2 and 8 items, excluding endpoints,” 2 and 8 are rejected and 3 through 7 are accepted. One changed word changes the tests.

Read documentation with a question

Write a specific question first: “What location does a relative filename use?” Find the official tool's matching documentation and check the version or operating-system context. Record the page title, URL and the relevant section. Restate the claim in your own words, then test a tiny example in a disposable folder. Documentation describes intended behavior; your experiment checks that you understood it in your environment.

A tutorial example is not automatically your requirement. A solution that accepts negative durations may be valid for that tutorial and wrong for our tracker.

Retrieve, check, transfer

After reading a short section, close it and write what you remember. Reopen it to correct omissions. Solve a changed example the next day. Record the correction as well as the initial attempt; a feeling of familiarity is not the same evidence as being able to explain and apply it. This is a practice procedure, not a guarantee about how quickly every learner will remember.

A useful help request

Use a fictional or sanitized example:

Goal: reopen a plain-text practice note. Environment: my desktop editor and file manager. Steps: created a notes folder, saved session.txt, then looked in notes. Expected: the file appears there. Observed: it is absent. Tried: inspected the editor's save path; it points to the parent folder. Question: should I move the file or change the path used by my next command?

For an actual program include the exact error and smallest reproducer, not just “it crashes.” Remove passwords, tokens and unrelated personal information. Say what help you want: a hint, a concept explanation or review of your hypothesis.

Using an AI tutor

Ask it to explain a term or suggest a diagnostic experiment. Preserve your prediction before seeing its answer. Verify the explanation against documentation or a small run; do not treat confident wording as evidence. Declare borrowed code and demonstrate the assessed skill without the generated solution.

Now complete domain D of the fresh reassessment. Use the Missing Semester shell introduction for the documentation exercise; no additional purchase is needed.