3 ms·

Man this is getting so goddamned ridiculous. Try to remember why Socrates cursed books. Oh, yes I'll wait while you navigate to, "Socrates-Books" in your Zette

• cue_the_strings 4y ago
  Tbh I use it rather differently, mostly for programming stuff. It makes sense to have the following things connected, for example: visitor pattern, std::visit, overload lambda template. Makes it easy to find related concepts and tricks. All bite sized snippets and explanations. It's also great for storing rarely used commandline snippets and tricks in a structured way, for things I use once in several years. Picocom and screen tricks and configs neatly connected to pages for old lab and network equipment, MIDI sysex tools and tricks connected to docs about certain FX processors and synths,... It's especially useful when you simply forget that you even had solutions for certain things, and that certain things are connected. I did so many vastly different things over the years that this seems to be the only way to efficiently jump back into something I haven't done in a while. I have a huge personal wiki (2000+ articles in vimwiki) which I'm now migrating to this tool, and there's one huge difference: I'm never sitting there thinking "How do I jam this new article into the wiki hierarchy... Oh, it's equally important for both of these categories...". I just jot it down in vim, add a couple tags, maybe a link or two, maybe find similar articles for inspiration if I don't know what to link to, and done. Extremely fast compared to a big vimwiki.
  • ncmncm 4y ago
    Funny "visitor" is about the only GoF pattern left in use, at least in C++ code. Ripe for disruption, by some measures.