<h1 id="catalogs">catalogs<a aria-hidden="true" class="anchor-heading icon-link" href="#catalogs"></a></h1>
<p><a href="/notes/cfx3cus8jl81qnm026xpnv3">type catalog</a><br>
<a href="/notes/i7ta88h1ch11xw328ehnbmj">color catalog</a><br>
<a href="/notes/psff2ci061yr6mz92uxzjil">UI components catalog</a><br>
<a href="/notes/3iwipeqgx0j5h1d85ub2nb9">UI design catalog</a><br>
<a href="/notes/h3zk70h0h1fk584x4c1p4mg">web design catalog</a><br>
<a href="/notes/3l0zqgem0zgbxpio7yubx04">algorithm design problem catalog</a><br>
<a href="/notes/uq8h51l9tu9fdaadikgwvid">algorithmic operations catalog</a>  </p>

catalogs

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

