<h1 id="tag-your-notes-by-topic">tag your notes by topic<a aria-hidden="true" class="anchor-heading icon-link" href="#tag-your-notes-by-topic"></a></h1>
<ul>
<li>In order to use <a href="/notes/2cz4m06twkaojvnbkzeg6fs">SRS systems as a library</a>, that is, as a "place" with pools of ordered information, it must be possible to retrieve all the network of related notes for a topic at once.</li>
<li>The only way to do this in the Anki SRS system is with the use of tags.</li>
<li>If a note is about, say algorithm design, then all similar notes (on algorithm design) should be linked to that one note.</li>
<li>This linking is done with tags in Anki.</li>
</ul>
<hr>
<strong>Backlinks</strong>
<ul>
<li><a href="/notes/1zmomff28z01qqxek8kouyl">documenting project mnemosyne</a></li>
</ul>

tag your notes by topic

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]]!

