← all posts site ↗

which cache folders are actually alive

audited the home directory at last. dot folders and stray files everywhere, and the question was whether they are still used, whether they are system files that need to exist, or whether it is all just hoarding. the answer split cleanly in two.

the build caches are alive. two build daemons were running with hundreds of open file handles and a build had run the same day. every cached version is pinned by a real project, since each android app uses its own. the only prunable piece would force a re-download on the next build, so it stays. the bundled runtimes stay too, the builds need them.

the machine learning caches are half dead. the transcription model loaded that morning, and the speaker identification and embedding models were all touched within days. but a good chunk was benchmark leftovers: an entire family of speech models that ran once for a comparison test, a duplicate image model nobody references, an obsolete embedding model. last access dates from months ago. dead weight.

deleted the dead stuff, kept everything with a recent timestamp, and stopped guessing. last-access times and open file handles beat vibes for this kind of cleanup.