My Knowledge Lakehouse
tabokie.github.io
My Knowledge Lakehouse
1–10 of 98 posts
Re: My Knowledge Lakehouse
#2I like the idea, and I do something similar but this has a lot of rules and feels more complex than potentially necessary. I personally use Obsidian.md as the tool for my Zettelkasten method. It provides back links and the like. I also create engineering journals for projects.
The only rule I have is to avoid unlinked notes.
Re: My Knowledge Lakehouse
#3There are some good ideas in here.
Personally I’ve abandoned all of my complex attempts at productivity and knowledge systems and have recently moved to the ever reliable txt file. You can format it however you want, use fun ascii art, or just plain paragraphs.
I’ve got a daily.txt where I prepend a new days section every day and put in whatever I want over the course of the day. I also create other files for courses I’m going through or projects as needed. The nice thing is using my editor I can make a file reference and hit gf and it’ll go right to a referenced file. But this “system” will keep on working regardless of what tools or system I happen to be using.
Re: My Knowledge Lakehouse
#4> 1.1221 Sometimes the primary tool is not available. An “always-on” secondary should take its place.
> 1.1222 Sometimes log from different tools or locations need to be “merged”, “persisted”.
These two are the main reasons I've stuck with Google Docs: It's available everywhere, and everything's always in-sync. Google already has all my info of value, so the incremental trust necessary to the threshold of log visibility is minimal.
I'll add one more requirement: I don't want to leave an unencrypted on-disk footprint containing my notes. This means I can access the entirety of my notes on any machine and the only thing I have to worry about is keylogging/screenscraping.
Google Doc is lacking in many respects, though. Linkability is nonexistent. Docs longer than 100 pages really struggle with latency on mobile. Searchability is bad (!) because you have to open the doc first to see the matches from within.
Really wish there was a self-hosted alternative with sync and encrypted storage that didn't result in sync errors. I've tried DEVONthink, Obsidian, LogSeq, Google Keep, Notion, NotesNook, GoodNotes, Samsung Notes, Loop, OneNote, Apple Notes, Org Mode, plain text files, and probably a dozen others... I'd say NotesNook is the best so far, with DEVONthink a close second, but, nothing beats the reliability, omnipresence and privacy of Google Docs.
Re: My Knowledge Lakehouse
#5Thanks for posting this. Currently building out something that is consolidating events from numerous sources and then automatically processing of those.
This post helped to give me some additional ideas on the processing of those events.
Re: My Knowledge Lakehouse
#6Very cool ideas! Very simple concept, indeed!
It helped to pin down my own approach, which is a very similar workflow, with these differences:
- The log entries are flashcards with ID
- The structure / tree follows the scientific method, aka the glue is not ad-hoc.
- So far I need no lists, because I only learn things and I'm not tracking any activity
Re: My Knowledge Lakehouse
#7There are some good ideas in here. Personally I’ve abandoned all of my complex attempts at productivity and knowledge systems and have recently moved to the ever reliable txt file. You can format it however you want, use fun ascii art, or just plain paragraphs. I’ve got a daily.txt where I prepend a new days section every day and put in whatever I want over the course of the day. I also create other files for courses…
It's clearly a nice and simple way to write data, but what about the other way around? How do you manage to find information when you need it?
Re: My Knowledge Lakehouse
#8This year I'm trying a new mechanism based around GitHub Issues (which I've been using for personal knowledge management for a few years already) - I create a new "planner" issue every day, then use that to make notes about what I want to do and what I've got done.
Hitting Command+N in Firefox on my Mac opens up my planner issue for the day, or creates it if one doesn't exist yet. I wrote up how that system works (a tiny bit of GitHub Actions + Pages magic) here: https://til.simonwillison.net/github-actions/daily-planner
Re: My Knowledge Lakehouse
#9> 1.1221 Sometimes the primary tool is not available. An “always-on” secondary should take its place. > 1.1222 Sometimes log from different tools or locations need to be “merged”, “persisted”. These two are the main reasons I've stuck with Google Docs: It's available everywhere, and everything's always in-sync. Google already has all my info of value, so the incremental trust necessary to the threshold of log visibil…
Syncthing + org-mode is the winning combo for me
Re: My Knowledge Lakehouse
#10There are some good ideas in here. Personally I’ve abandoned all of my complex attempts at productivity and knowledge systems and have recently moved to the ever reliable txt file. You can format it however you want, use fun ascii art, or just plain paragraphs. I’ve got a daily.txt where I prepend a new days section every day and put in whatever I want over the course of the day. I also create other files for courses…
It's clearly a nice and simple way to write data, but what about the other way around? How do you manage to find information when you need it?
Read data? lol it is usually just a write only system (aside reviewing the current info from the week).
But since it is all in one place I just do search queries using my editor to find what I need. I don’t use tags, but it would be very simple to just append some #tags in my content and search for those.