日记与引导式写作
1 分•作者: grandimam•6 天前
我用 Notion 写日记好几年了，但我发现切换到它的 DSL（领域特定语言）的认知成本对我来说不划算。Notion 基于块构建，比如建立在块之上的数据库。即使我将笔记导出为 Markdown 格式，它仍然反映了 Notion 的内部数据结构，而不是给我一些干净且可移植的东西。
例如，内联数据库最终会变成一个表格，其中包含指向文档其他部分的 href 链接——很好，但当我想要可以实际使用的纯文本时，它就不是很有用了。
与此同时，我一直在进行大量的提示，而 Markdown 更适合我的工作流程。它不是一个日记工具，但它简单且被广泛支持——GitHub、VSCode 等，并且它消除了使用专用笔记应用程序带来的许多上下文切换。
我可能会怀念的是内联数据库和其他丰富的内容，但我已经学会了停止使用它们。但是，我已经将我的日记工作流程优化到很多我的提示技巧。我使用常规表格并更刻意地拆分文档。如果需要，我会在日记之间引用它们，有点像为工作流程的每个部分设置了专门的提示。
我还在日记中使用许多提示技巧——我使用常规表格（更扁平且未链接）而不是创建内联数据库，并开始更多地拆分文档，并在我的日记中引用它们。
我有时也会在顶部放置 YAML 前置元数据和描述。这样，如果我想要运行一个 LLM 来处理我的日记——用于总结年份或构建语义搜索——我已经准备好了。（甚至可能将其变成 https://gpt.qalam.dev 的一个功能）
我意识到工具的重要性不如我组织思想的方式。
查看原文
I used Notion for several years for journaling, but I found the cognitive cost of switching into its DSL wasn’t worth it for me. Notion is built on blocks, things like databases built on top. Even when I exported my notes to Markdown, it still reflected Notion’s internal data structure instead of giving me something clean and portable.<p>For example, the inline database ends up as a table with href links to other parts of the document - nice, but not very useful when I want plain text I can actually work with.<p>Meanwhile, I have been doing a lot of prompting, and Markdown makes more sense for my workflow. It is not a journaling tool but it is simple and widely supported - GitHub, VSCode, etc and it eliminated a lot of the context switching that came with using dedicated note-taking apps.<p>What I would miss probably is the inline database, and other rich content which I have learned to stop using. But, I have optimized my journalling workflows to a lot of my prompting techniques. I use regular tables and split documents more deliberately. I reference them across journals when needed, kind of like having dedicated prompts for each part of a workflow.<p>I use the a lot of the prompting techniques in journalling as well - instead of creating inline database, I use the regular tables (more flattened and un-linked), and started splitting documents more, and referencing them in my journals.<p>I also sometimes put YAML frontmatter at the top for metadata and descriptions. That way, if I ever want to run an LLM over my journals - for summarizing the year or building a semantic search - I am already set up. (Might even turn that into a feature for https://gpt.qalam.dev)<p>I have realised the tool must matter less than how I structure my thoughts.