Teaching chmod Without Teaching Fear

We stopped opening permissions courses with recursive examples because they teach panic instead of pattern recognition. The first week now anchors on POSIX basics written out longhand, with mentors marking up each stanza of a change plan before any command runs.

In the second week, learners inherit intentionally messy trees from a fictional city hall migration. They must narrate each chmod decision aloud in a shared doc—a little theatrical, but it surfaces assumptions faster than silent terminals.

By the third week, ACL edge cases appear beside a deliberately vague stakeholder request. Learners draft two responses: one technical, one operational, swapping critiques in pairs.

We close the arc with a dry-run review where mentors pose as grumpy auditors who only accept evidence-backed rationales. That closing heat is what keeps chmod from becoming muscle memory without meaning.