Organizing snippets with collections

Folders force a choice: a snippet lives in one place, so you file it under React and then can't find it three weeks later when you're thinking Interview Prep. The thing you saved is real; the single location you filed it under was a guess.

Collections drop the constraint. An item can belong to as many collections as make sense, so you organize around how you'll look for something rather than where it came from.

One snippet, many homes

A well-written useDebounce hook is a React pattern, an interview talking point, and a performance trick all at once. Put it in all three collections and it surfaces wherever your head is at that moment.

Structure that scales

• Keep collections intent-shaped — React Patterns, Interview Prep, DevOps — not source-shaped.
• Let items overlap freely; overlap is the feature, not a mess to clean up.
• Lean on search for the long tail and collections for the handful you revisit constantly.

Collections are for the things you return to on purpose. Search is for everything else. You need both.

Start with three or four collections you'd actually open. Add items as you go, drop them into whatever fits, and let the structure grow out of real use instead of a taxonomy you designed up front.