<h1 id="anki-as-journal">anki as journal<a aria-hidden="true" class="anchor-heading icon-link" href="#anki-as-journal"></a></h1>
<ul>
<li>When an Anki deck is categorised by time, it is possible to use the deck to recall the group of topics one was involved in during certain periods.</li>
<li>From the topics/questions, you can imagine where your headspace was, what you were majorly thinking about and even adjacent "events" that you probably didn't pay attention to.</li>
</ul>
<hr>
<strong>Backlinks</strong>
<ul>
<li><a href="/notes/1zmomff28z01qqxek8kouyl">documenting project mnemosyne</a></li>
<li><a href="/notes/b0flxzhvnxhpuc9w8eca3hi">how should anki decks be organized</a></li>
</ul>

anki as journal

Dendron


You've stumbled on [Caleb's](https://bycaleb.wasegun.com/) public notebook. You can conceive of this as a sketchbook too—i.e., rough, incomplete, and sometimes sparse. Hence, you might not get the full-gist of any one random page in the notebook. It is meant to help me elaborate/consolidate on my work & thoughts as a software engineer. This is not quite a [digital garden](https://maggieappleton.com/garden-history), and also unlike [Andy's working notes](https://notes.andymatuschak.org/About_these_notes).

I built this (experimentally & publicly) with [Dendron](https://www.dendron.so/), specifically, to understand if & how "quick, linked, and atomic" note-taking can help realize, remember, & learn (how to make better) design decisions when working on quick (or slow) software engineering projects. Of course, it does help—that makes this is a demonstration of exactly how it helps.

Check out my growing list of [[projects]]!

