✳flâneur — a map of the web's best reading

Introducing My Knowledge Lakehouse

tabokie.github.io · 768 words · saved by 1 readers

1.111 entry can be anything really: an idea, a memory, a piece of information, a progress update of a task, a TODO item, a reference to another entry… 1.12 Immediacy and immutability matters. entrys are captured as they happen, never modified. 1.121 There’s no room for auditing or forgetting. entrys are an authentic reflection of reality. 1.122 Efforts should be put to optimize the latency of the capture. 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”. The general principle is to reduce manual steps (e.g. use a Web App that merges automatically), and do them daily at a fixed time and place (e.g. push to a git repository before going to bed). 1.123 In this sense, log is very similar to Lab Notebooks (Sam Bleckley, 2020) 1.13 External context (if any) is part of the entry. 1.131 At the minimum, the title, author, and year of publish should be cited.

Introducing My Knowledge Lakehouse | Xinye Tao Introducing My Knowledge Lakehouse # non-fiction, 2024-01-13 1 There’re only three entities: log , list , structure . 1.1 Everything goes into the log chronologically. It is the source of truth. 1.11 We refer to the smallest unit of content in log as entry . 1.111 entry can be anything really: an idea, a memory, a piece of information, a progress update of a task, a TODO item, a reference to another entry … 1.12 Immediacy and immutability matters. entry s are captured as they happen, never modified. 1.121 There’s no room for auditing or forgetting

Explore this link on the map →

related reading