Development Environment: Mistake Clinic
Use one actual mistake or one deliberately seeded failure from the required practice. Label a seeded case; do not invent personal mistakes to meet a quota. This review is included in the module allowance, and reuses existing artifacts.
Module-Specific Mistake Radar
- Right filename, wrong folder: record the working directory and predicted relative path; reproduce failure, then change the starting point or path and explain why it works.
- Unquoted space: inspect argument boundaries with
printf '<%s>\n'; repair the original invocation, not only the script's use of$1. - Wrong count: distinguish matching lines, unique files and occurrences. Use one file with two matching lines to disprove a file-count claim.
- False success: a missing file piped into a counter can print 0; preserve stderr and inspect the correct command status. Explain why the guided lab's input redirection fails instead.
- Alias survives deletion: changing configuration text and changing live shell state are different operations; demonstrate the difference in the disposable child shell.
- Saved the wrong file: compare editor save location with the file reopened by your command, then preserve and repair the mismatch.
Practice Mistake Checks
Keep the original command or prediction, actual output/status, a hypothesis, the smallest check that distinguishes it from an alternative, the repair and a fresh case. For example, if changing only the working directory changes the outcome, reinstalling the editor is not supported by that observation.
A passing clinic has a reproduced failure, an explanation consistent with the evidence, a demonstrated repair and successful fresh transfer. If you cannot explain why the repair works, return to the matching concept. No five-error quota, previous-semester skill, speed improvement or proof-writing requirement applies to this beginner module.
Use worked examples for calibration and practical checks for progression. Do not create a second portfolio of the same evidence.