3 ms·
Without too much effort, I keep a NOTES file in each project directory. I keep it out of source-control. Anything that is worth preserving (backed up and checke
by _nato_ 8y ago
Without too much effort, I keep a NOTES file in each project directory. I keep it out of source-control. Anything that is worth preserving (backed up and checked in) goes in README. I also use a file called SCRAP for ephemeral matters, again, in each project root, not checked in. A great pattern that has served me well.
- ah- 8y agoI do the same. A simple text file that's not in git, structured a bit like markdown. I keep it open in vim, so it's always there when I need it. I've tried using more complex tools like vim outliner and evernote, but simple text files work better for me.
- dwaltrip 8y agoGreat system. I do something similar by creating a "_misc" folder out of source control. The "_" is so that alphabetically it is listed at the top and not intermixed with actual project folders. I use it to store code snippets, prototyping scripts, misc notes that don't fit in my main folder system for notes/todos, query output, and other random items. If the _misc/ directory becomes too cluttered , then I throw most of the items into an "archive_$DATE" sub-directory (inside _misc). I'm still working on a broader, general organization system for notes, documents, links, todos, etc... (lots of good ideas in this thread). But this works well for more ephemeral project-specific stuff.