From 9e314a638565d09b82574ce983329df1bd2857f3 Mon Sep 17 00:00:00 2001 From: June Gardner Date: Tue, 18 Nov 2025 12:12:45 -0800 Subject: [PATCH] Added some art. --- docs/log/2025/11/18/index.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/docs/log/2025/11/18/index.md b/docs/log/2025/11/18/index.md index 16f3c26..cab7ac2 100644 --- a/docs/log/2025/11/18/index.md +++ b/docs/log/2025/11/18/index.md @@ -16,6 +16,18 @@ That's the common (in my eyes) definition: bringing up a system from some prereq # Dependencies +``` + _-_ + /~~ ~~\ + /~~ ~~\ +{ } + \ _- -_ / + ~ \\ // ~ + | | + | | + // \\ +``` + In my mind, a bootstrappable system is something that can be *understood from nothing* (or at least, some common base). That someone could walk in, fresh, knowing some set of concepts, and be *assured* that they can understand the system. That's pretty common, right? There's a common "dependency tree" of concepts that everyone kind of takes for granted when they work on a project or in a field. But I don't think many of us have an eye on what that dependency tree is (in many cases, it's really a cyclic dependency graph). @@ -28,6 +40,6 @@ When the abstractions were thin, and the hardware was "weak" (giant airquotes he I have not seen these dependency trees shrink without sacrifice. I have not seen the cognitive load lessen, only become more obscure. I am tired of looking around and seeing invisible skyscrapers. -I want a bootstrappable system so I can use it when I am exhausted, when I forget, when life calls me away, I can rebuild my understanding without thinking too hard. I want to be able to understand it all at my weakest, and yet feel I still have control. +I want a bootstrappable system so I can use it when I am exhausted, when I forget, when life calls me away. I want systems I can rebuild my understanding of without thinking too hard. I want to be able to understand it all at my weakest, and yet feel I still have control. Anything less, I won't be satisfied. -- 2.39.5