&gt;  I&#x27;d argue that most of those are acting like FILO queues anyways, since you typically don&#x27;t need random access to clothes in a washing machine&#x2F;from the to-be-washed pile.<p>Except in emergencies. But I regularly need stuff from the &quot;hanging on the clothes drier&quot;&#x2F;&quot;in the basket ready to come upstairs&quot;&#x2F;&quot;in a big pile on the end of the bed ready to be put in the wardrobe&quot; ones.<p>&gt;  but it isn&#x27;t caching as described in the article,<p>It&#x27;s still caching. It&#x27;s just a prefetch cache - using quiet time to prefetch my clothes for when they are needed very quickly.<p>&gt; so excellent organization is (probably) the best way to cut down on overall time.<p>I&#x27;m not sure it is. Excellent organisation has quite a write-time overhead. In most cases, the amount of effort to organise everything perfectly is going to outweigh the fractional time saving I&#x27;d get on most mornings.<p>And in this case I&#x27;m also not looking to optimise overall time. I&#x27;m specifically looking to optimise speed to access it in the morning.<p>&gt;This is _still_ not caching, since you weren&#x27;t going to sit down and perform some access intensive operations on your wallet and keys in the morning,<p>I would be. If I had to go and get my single credit card from the filing cabinet where I keep the rest of them, then go and get my work pass from a &quot;work&quot; pile, my keys from the key box, my coat from the closet, my shoes from the shoe cupboard, my bus pass from my transport drawer, my daughter&#x27;s school bag from her school-related pile  etc, etc.<p>The author makes it pretty clear that he&#x27;s talking about caching in exactly this way<p>&quot;Caching is such an obvious thing because we do it all the time. I mean, the amount of information I get . . . certain things I have to keep track of right now, a bunch of things I have on my desk, and then other things are filed away, and then eventually filed away into the university archives system where it takes a whole day to get stuff out of it if I wanted. But we use that technique all the time to try to organize our lives.&quot;<p>At the end of the day, it&#x27;s never going to be a cache in the true computer sense of the work - there&#x27;s not a separate copy being made (except in the case of my keys, where I&#x27;ve got exactly that, but that&#x27;s more for failover than for caching) - but the idea of grouping things by speed of access in a given scenario rather than by category is analogous enough to caching to be worth discussing.<p>If you want to call it &quot;locality of reference&quot;, that&#x27;s fine (and the link even talks about caching as one form of it). But one critical factor of an analogy is that it&#x27;s a reasonably well understood term, and I strongly suspect that a lot more people would understand cache than locality of reference.