notes-vault: piling the commands and syntax I keep looking up into one cheat-sheet library
notes-vault is my own cheat-sheet notes library, one repo where I stash the stuff I keep having to look up. Rust ownership, how to slice fields in awk, gdb conditional breakpoints, some SQL window function, things I’ve searched a hundred times and still can’t remember, so I search again every time, and only after searching do I realize I looked at the exact same thing last month. So I just started a repo to keep them, and look things up as I need them.
No static site, no full-text search, no fancy theme, none of that. The value of notes is in the content, not the shell, and the heavier the shell, the lazier I get about actually filling it. What I landed on is the most primitive option: one notes/ directory, one md per topic, nothing to build. Want to read it, cat it; want to find something, grep it; click into it on GitHub and it reads fine too; clone it and you’ve got the whole thing. Zero overhead is exactly why it survives.
git clone https://github.com/dwgx/notes-vault.git
cd notes-vault
ls notes/ # what topics are there
cat notes/vim-cheatsheet.md # flip through one
grep -ri "rust" notes/ # grab a keyword across everythingInside are the usual piles I keep running into. Language features from Rust ownership, Go concurrency, Java streams, Kotlin DSLs to TS generics, JS async, C++ templates, plus a heap of Python; the functional set of closures, map/filter/reduce, partial application; command line awk, sed, grep, find, curl, jq, tmux, ssh tunnels; frontend React hooks, flexbox; toolchain Docker, nginx, CMake, gdb, Git, Vim; data odds and ends SQL, regex, memory-leak hunting, performance tuning.
Honestly a lot of the files are still placeholder skeletons right now, the title standing there with the content filled in slowly. It’s a scratchpad, not a systematic tutorial, patched as I go. As long as I can find it and copy it out, that’s enough for me, no more digging through browser history. Public, MIT, take whatever.