<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@mcc" class="u-url mention">@<span>mcc</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.transneptune.net/@owen" class="u-url mention">@<span>owen</span></a></span> </p><p>Thinking of an elderly friend whose living room is lined with file cabinets, from a career keeping folders of teaching materials, who to this day struggles with the distinction between a "file" and a "document", even though they've been strategically saving documents with iterating file names for years to avoid overwriting old work.</p><p>One barrier to comprehension: the idea of nesting folders working like Matryoshka dolls. This is someone with decades of real world experience with files and folders, and in their real world experience, there's only ever three levels of nesting, a manila in a pendaflex in a drawer.</p><p>Even the suggestion that drawers are nested in cabinets is enough to derail understanding.</p><p>Another, that files exist independent of the program that created them. Trying to find a PDF file after using the scanner, and confused that it doesn't turn up, because they've tried to find it via the Open File dialog in Word. "That is how I get to my files."</p>
