4 ms·
The most simple but one of the most effective tricks I learned from an "old sweat" when I was a green junior dev just starting out... keep a folder called notes
by Simon_O_Rourke 3y ago
The most simple but one of the most effective tricks I learned from an "old sweat" when I was a green junior dev just starting out... keep a folder called notes, and each day create a date-numbered file in the format YYYYMMDD.txt.
Put any code snippets, git links, lessons learned, meeting minutes or basically anything interesting in there each day.
Then to access it - you can bash script search, e.g., to find anything you wrote in 2022, you'd simple type;
grep "whatever" 2022*.txt
It works like a charm, been using it for fifteen years.
- louwhopley 3y agoThe simplicity of this is remarkable. Dropbox-like tools can also ensure it gets backed up to the cloud.
- flandish 3y agoI basically do this too but also do it in markdown and use Obsidian to link to others, etc. Still hit the cli though and grep/ripgrep all the time, it’s just so fast.
- BrandoElFollito 3y agoThis is what I use with Logseq. A new nie created every day and the added before of tags to gather the various points together. I built dly (https://github.com/wsw70/dly https://github.com/wsw70/dly) to make one line notes taking faster.
- orev 3y agoVimwiki essentially does this for you with the diary feature, and it also allows some nice wiki markup, including todo items you can mark as completed.
- stnmtn 3y agoI do this except with only one text file, with a separator for M/D/Y so I can always have the date I find it easier to follow tasks if I can scroll up a bit to the previous day and see if any tasks are being left undone for a couple days. I can just drop that task if I realize it's not important, but having it right there in front of me is very useful I've found.