Write the reason before the quote

My reading setup has shifted almost entirely to audio over the years. I predominantly listen while cycling, which is often the only uninterrupted stretch I get — and whenever something lands, I stop the bike, pull out my phone, copy the quote, and dictate my reaction into speech-to-text; my OpenClaw agent picks it up and creates a SlipBox note in my ZK folder. The capture part is solved, more or less. The harder problem is what to actually write down: it's difficult sometimes to be disciplined enough, or have the right environment, when you come across something interesting.

• Simply copying the content from different sources will get you a SlipBox full of somebody else's ideas, not your own.
• Sönke Ahrens's How to Take Smart Notes offers one answer: write down what surprised you or changed your thinking, not a summary. That holds for almost any kind of writing. You don't have to constrain yourself to fleeting/literature/permanent notes if that structure doesn't fit your workflow.
• When I come across something I want to note, I write my reason for creating that note first, then the direct quote. It makes it more interesting to find later (I can compare my reasoning with what the reference actually says, and they're rarely the same).

What you're actually reading for shapes all of this — whether you're building an argument over time, a reference you'll search later, or something else. Getting that clear is the step most frameworks skip.

Yours, from a smaller system,
Zhenia