<h1 id="describe-the-current-extent-of-your-work-on-tools-for-thought">Describe the current extent of your work on Tools For Thought<a aria-hidden="true" class="anchor-heading icon-link" href="#describe-the-current-extent-of-your-work-on-tools-for-thought"></a></h1>
<p>What I've done is better described as personal experimentation. And the outcome of that is an introductory experience of the basic insights the field builds upon.</p>
<hr>
<strong>Backlinks</strong>
<ul>
<li><a href="/notes/j9oj7sz92eze98leifzbkiy">FAQ</a></li>
<li><a href="/notes/38c1357vt1wney3gs5jp1wb">what are Tools for Thought</a></li>
</ul>

Describe the current extent of your work on Tools For Thought

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

