You know that thing folks get sometimes where they're having a technical problem, they look it up online, and the top relevant hit is one of their own blog posts? And it does in fact answer the technical question?
I just had something like that, but for code I was trying to figure out, and instead of a Web search it was grepping through a folder of checked-out projects.
Oh.
I wrote the code to do this exact thing two years ago.
I frequently consult my own book about linux admin, because I have no memory of how to use things like parted and lv-extend
I've got a 200 page google doc called JT-cookbooks. It's just a bunch of weird disorganized invocations. It's become a first reference for lots of my coworkers.
Writing down things that work matters more than any management types would believe.
@johntimaeus that's a big part of why I pulled my toot and tweet archives into my notes. I tend to dump stray thoughts as sort of an ADHD venting mechanism. Problem is some of those thoughts are good, and Twitter / Mastodon search has never been great.
Course, new problem. My public brain now has 6,000 pages and weighs 4.5GB without optimizations.
Working on that now.
I'm wondering how many people around here have an equivalent, and what it would take to aggregate, organize, edit, verify and publish as a collected work.
Most of mine are recipes, 1-5 lines to build a thing, or fix an issue. "Fix chrome silent fail on cloned VM" is one I added today. But you'll spend an hour flopping at Google trying to find a fix before hitting the one that works. You may also break a lot of other stuff listening to crackoverflow and AI plop.
Random Geek
John Timaeus
pfriedma