11 · Life Plan
The Master Plan
The foundation of this entire site.
Eighteen Parts with roughly 880 pages. On identity, my ten technical domains, the build-to-understand loop, my AI usage constitution, phases, the season structure, and the first ninety artifacts. All published here for accountability.
18 Parts · read in order or jump in →
Current Tasks
What I'm currently working on.
All aligned with the master plan. Things I'm getting done but not necessarily everyday. Finer than the Master Plan's artifact backlog. Every item here is something you can ask me about. Each varies in difficulty and length. All published here for accountability.
112 total · 106 open · 0 in progress · 6 done →
Understand deeply. Build honestly. Ship publicly. Serve usefully. Repeat forever.
Philosophy
five operating principles
This rule cures a pattern that I've had for years. I would watch, read, talk and somehow leave no record of any of it. Interest with an artifact, leads to understand which with time, leads to competence.
All the artifact has to do is exist. It doesn't need to be adequate.
Small artifacts can compound. A streak of small artifacts become a body of work. And a body of work is the only honest claim that learning happened.
This identity is not aspirational. It is operational.
Every domain in my life has a doing form. I haven't practiced a domain if I can't point at things I produced in it.
The reverse is also a rule. I do not build without studying the canonical source. I do not ship without testing. I do not publish without revising. For me, the builder, researcher and engineer angles are all in one.
The longer version: The AI Usage Constitution
The short version: There is always a downside. AI compresses time, in turn for knowledge.
I refuse to produce and not grow myself. The fastest path to competence is also the fastest path to no competence. Can I explain it to a child? Or even myself, for that matter?
I sometimes do something at unsustainable speeds to then abandon it, or wait for the perfect moment to start that never comes.
A day's work isn't the goal, a week is. A month's worth may produce little, a year can change your lifetime.
Summaries are a translation. Every translation loses something.
A YouTube video about a paper is not the paper. A blog post about Linux internals is not the kernel source. A tutorial on calculus is not the textbook by the mathematician who taught the course at MIT.
Summaries help scaffold. They do not build foundations.