写日记与提示
我使用 Notion 进行了几年的日记记录，但我发现切换到它的领域特定语言（DSL）所带来的认知成本对我来说并不划算。Notion 是基于区块构建的，诸如数据库等内容都是在其上构建的。即使我将笔记导出为 Markdown，它仍然反映了 Notion 的内部数据结构，而不是给我一些干净且可移植的内容。
例如，内联数据库最终变成了一个带有指向文档其他部分的超链接的表格——虽然不错，但当我想要可以实际使用的纯文本时，这并不是很有用。
与此同时，我一直在进行大量的提示工作，而 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.