> The second is absorption: mental models form, edge cases become intuitive, architectural relationships solidify into understanding. ... . The friction of implementation creates space for reasoning.
> This gap between output velocity and comprehension velocity is cognitive debt.
I have felt that lack of absorption during the last months, adding doomscroolling to the equation, I have felt how my thinking is disappearing.
I tried to speculatively expand that idea in this post
> A species that cannot follow the reasoning of its own systems does not supervise them; it simply inhabits them until they stop working.
I feel this idea is closely related to additive bias. People are scared of breaking things, so the safest way is to just add another tiny part to an already complex system. As cognitive debt accumulates faster, this additive bias just becomes stronger imo.
I agree, the LLM support we lose some level of manual work, maybe that is useful to be more familiar with the information, although I am not sure if that is a critical step. The LLM gives us management support. We can use a command to collect incomplete tasks, the LLM is doing that with extra steps, and it shows us the collected information, but in the end, we decide which tasks to prioritize.
Inbox Processing Workflow - GTD-style system to keep your inbox at zero, with AI classification of notes to projects, resources, or someday/maybe lists.
Incomplete Tasks Review Workflow - weekly review that analyzes your tasks, identifies gaps, detects duplicates, and generates a focused "plan of attack" with your highest-priority actions.
Both workflows combine classic productivity principles (GTD, weekly reviews) with AI assistance to reduce cognitive load and maintain system trust. They use command-line tools (find, ripgrep) to analyze your vault and generate processing recommendations in an easy-to-review card format.
Use at your own risk. Validate each command before executing it. It is strongly recommended to use a version control system (Git) in your Obsidian vault to visualize and revert changes made by the agent.
Any suggestions to improve these workflows are appreciated.
I'd enjoy seeing a video of this being used in the intended way and to good effect (because I'm confident that my conception of how it works is inaccurate).
> This gap between output velocity and comprehension velocity is cognitive debt.
I have felt that lack of absorption during the last months, adding doomscroolling to the equation, I have felt how my thinking is disappearing.
I tried to speculatively expand that idea in this post
https://news.ycombinator.com/item?id=47186004
reply