<h1 id="split-linked-list-in-parts">split linked list in parts<a aria-hidden="true" class="anchor-heading icon-link" href="#split-linked-list-in-parts"></a></h1>
<p><a href="https://leetcode.com/problems/split-linked-list-in-parts/">https://leetcode.com/problems/split-linked-list-in-parts/</a></p>
<p><img src="/assets/images/split-linked-list-in-parts.jpg" alt="split-linked-list-in-parts">  </p>
<hr>
<strong>Backlinks</strong>
<ul>
<li><a href="/notes/3l0zqgem0zgbxpio7yubx04">algorithm design problem catalog</a></li>
</ul>

split linked list in parts

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

