<h1 id="why-learn-algorithm-design">why learn algorithm design<a aria-hidden="true" class="anchor-heading icon-link" href="#why-learn-algorithm-design"></a></h1>
<ul>
<li>It is fun!</li>
<li>"It is usually the case that when engineers learn algorithm design, they do so not primarily because it is fascinating to think about technical problems but because getting a FANG job is a big motivation. The prospects of getting a FANG job doesn't excite me anymore. I just, now, want to reach back to that initial spark that made me find something really fascinating about the implementation of computer algorithms. The genesis, most of the time is mathematics. The beauty of it. The promise that by understanding some fact deeply, you can see and appreciate its beauty in some other thing."</li>
</ul>
<hr>
<strong>Backlinks</strong>
<ul>
<li><a href="/notes/6t1kh5r5dr6hn6a9rcb76cc">documenting p-knuth</a></li>
</ul>

why learn algorithm design

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

