This article is meant to test how the template renders markdown
the problem with saving everything
every few months i nuke my downloads folder. not bc i'm organized but bc i've accumulated like 40gb of pdfs i'll never read and youtube-dl artifacts from 3am research spirals. the thing is - and this is the REALLY bleak part - i know exactly what i'm doing when i save this stuff. i'm building a little digital mausoleum of intentions.
there's this thing where people confuse having information with knowing it. like your boy wittgenstein said something about how if a lcion could speak we wouldn't understand it anyway. same energy as hoarding 500 articles about bayesian statistics when you still can't explain bayes' theorem to your mom.
the data hoarding subreddit will tell you you need a proper taxonomic system. they'll recommend obsidian with seventeen plugins, notion databases with relational fields, or some bespoke zettelkasten implementation that requires learning vim keybindings. the setup takes longer than actually reading anything.
here's what a typical "knowledge management system" looks like in practice:
| folder name | actual purpose | files added this year | files opened this year |
|---|---|---|---|
reference/ | guilt repository | 247 | 3 |
to_read/ | procrastination inbox | 891 | 0 |
projects/ | abandoned dreams | 156 | 1 (by accident) |
archive/ | double guilt | 2,341 | 0 |
you're not building a second brain. you're building a second anxiety.
the cope of "someday i'll organize this"
afaict we're all just LARPing as the kind of person who maintains a zettelkasten. you bookmark that article about building a second brain, you download logseq or obsidian, you spend 6 hours configuring plugins instead of actually writing anything. peak cargo culting.
the actually USEFUL stuff? you remember it bc you used it. everything else is just aesthetic signaling to your future self that you're Intellectually Serious™.
consider the things you actually know how to do:
- stuff you use daily (no notes required)
- stuff you learned by breaking it repeatedly
- stuff someone explained to you three times while you were actively confused
- that one thing you had to teach someone else
conspicuously absent from this list: "things i saved to notion in 2019."
"We are what we repeatedly do. Excellence, then, is not an act, but a habit." — Aristotle (or Will Durant, depending on how honest you want to be about misattribution)
the neuroplasticity research is pretty clear on this: retrieval practice beats passive review by like 300%. you don't internalize information by highlighting it in different colors. you internalize it by failing to recall it, struggling, then reconstructing it from scratch. this is why tutoring works and why rereading your notes doesn't.
but rereading notes feels productive. it's frictionless. your eyes move across familiar words and your brain goes "yes yes i recognize these symbols" and you get a little dopamine hit. meanwhile the actual skill (being able to generate the insight without the notes) atrophies.
what actually works (probably)
idk man just write more and read less. sounds fake but the ratio of input to output for most people is completely cooked. you don't need another article about [insert topic], you need to actually try the thing and document what breaks.
!
this is why substack guys who write weekly essays seem weirdly knowledgeable compared to ppl with 10TB media servers - they're FORCED to synthesize and can't just endlessly accumulate slop.
here's the actual workflow that works:
- encounter problem
- try obvious solution
- obvious solution fails (document why)
- google frantically, find three contradictory stackoverflow answers
- try all three, document which one worked
- write up what you learned immediately while it's still painful
- now you actually know it
vs the broken workflow:
- think "i should learn [thing] someday"
- save 47 articles about [thing]
- never open them
- feel guilty
- organize them into a better folder structure
- still never open them
- repeat until heat death of universe
the psychological term for this is completion bias - your brain treats "saved for later" as equivalent to "processed and understood" bc the dopamine systems don't distinguish between "acquired resource" and "utilized resource." evolution didn't optimize for information abundance, it optimized for caloric scarcity. your brain thinks hoarding pdfs is the same as storing winter fat.
notable exceptions where archiving actually matters:
- primary sources - original research papers, historical documents, datasets. things that might disappear or get paywalled.
- technical specs - API docs for deprecated software you still maintain, hardware datasheets, protocol RFCs.
- personal artifacts - your own writing, code, photos. stuff you made that has intrinsic value independent of "learning."
everything else? probably fine to let it go.
the cope of "but what if i need it later"
the classic justification: "what if i need to reference this obscure postgresql optimization technique in 2027?"
brother. be real. you will:
a) google it again when you need it (probably finding better info bc the field advanced)
b) not need it bc the problem domain shifted
c) need something adjacent that your saved article didn't cover anyway
the only time saved references are actually useful is when you've built enough context that you know WHERE to look. which requires... already understanding the domain. which requires... doing the thing, not reading about it.
this is why experienced engineers can find solutions fast - not bc they have better bookmarks, but bc they've internalized the shape of problems. they know what to google. their mental index is "this feels like a connection pooling issue" not "i saved an article about connection pooling in 2019, let me find it."
conclusion (if you can call it that)
anyway the point is: your carefully organized folder structure is a lie you tell yourself. just accept the chaos and grep your way to victory like god intended.
or if you absolutely must maintain an archive, at least be honest about what it is: a security blanket, not a productivity tool. there's nothing wrong with keeping a comfort collection of interesting pdfs. just don't pretend it's making you smarter.
the real move is writing everything down after you do it, not before. post-mortems beat pre-mortems. ship logs beat sailing manuals. your future self doesn't need your bookmarks, they need your scars.
now if you'll excuse me i have 1,847 browser tabs to feel guilty about.