Spent the morning reorganizing my project folders, and it reminded me why I keep coming back to the three-folder rule. The light from my desk lamp was catching all the dust on my keyboard—guess that's another task for later—but I stayed focused on the cleanup.

Here's what actually works: create three top-level folders in every project. Source for code and raw files, Build for compiled outputs, and Docs for everything else. That's it. The moment you add a fourth category, you start second-guessing where things go.

The checklist:

• Delete files you haven't touched in 90 days (be ruthless)
• Name folders with dates: 2026-03-project-name
• Keep a single README.md at the root
• Use a .gitignore from day one

The common mistake? Creating folders for "maybe later" or "misc." I did this for years. Those folders become digital junk drawers. If you can't name it clearly, it probably doesn't need a folder yet. Just keep it in the parent directory until you have three or more related items.

I moved about forty files today and realized I'd been saving duplicate downloads for months—same PDF, five different names. That taught me to check the file size before saving. If it's suspiciously similar to something else, it probably is.

Maybe I should automate this, I thought halfway through. But honestly, the manual pass forces you to see what you've been hoarding. Automation can come later once you know your patterns.

Your tiny task: Open your Downloads folder right now. Delete three files. Just three. Notice how much easier it gets after the first one.

The room feels clearer already, and I didn't even vacuum yet.

#organization #productivity #digitalcleanup #workflow