The Why · 10 posts
Quest Engine
The model itself: Search, Drive, and Renew, the Why, the four Ws, and how they fit together.
Blog
This is one body of work organized into four editorial tracks. Each track keeps a stable voice and reading rhythm, while tags connect related ideas across the whole collection.
Subscribe to the RSS feed to stay updated with new posts.
Editorial Tracks
Every post belongs to one track with its own subject, reading rhythm, and voice. The tracks follow the Quest Engine's own outline: the model, the record, then Search, Drive, and Renew. Tags connect ideas across tracks.
The four Ws · 9 posts
Field Notes
Personal history, retrospectives, portfolios, and observations from work in progress.
Search: mastery · 24 posts
Software Engineering
The craft and career: languages, code, verification, agent workflows, judgment, and growth.
Drive: autonomy · 25 posts
Engineering Systems
How teams and organizations work as systems: incidents, ownership, risk, context, and the words engineers use.
Renew: purpose · 17 posts
Human Systems
The person as a system: cognitive (attention, habit, motivation, meaning), physical (the body, energy, rest), and health (sleep, stress, burnout, recovery).
Agents Are Taking the Drive
Roughly 80% of the software I produce now starts as a prompt, not a keystroke. Mapped onto the Quest Engine, that means agents have moved into the Drive (the How) and are eating into the four W's. What is left for me is the Why, the context still trapped in people's heads, and the work of running a fleet of agents predictably.
Elon's Algorithm: A Reference for the Manual Process
A reference write-up of Musk's five-step algorithm and what each step is supposed to mean when the thing being improved is a manual process in software engineering. Question the requirement, delete the step, simplify, accelerate, automate. Mostly a description of what the algorithm claims rather than an argument that it is correct, with a short closing note on where I do agree, in particular the rule that if you are not occasionally adding things back you are not cutting enough.
From Manual to Self-Sustaining: The Quest Engine Path
Elon's algorithm is not really an automation algorithm. It is a procedure for forcing shared understanding of a process, and automation is what it happens to permit at the end. The Quest Engine says the same thing structurally and translates it to a world that is mostly digital, where the walk around the factory floor can be delegated to agents and the goal is not a fully automated process but a self-sustaining one that keeps humans only where judgment genuinely lives.
Joy, Freedom, Motivation: Matz's Triad and the Quest Engine
In a conversation about Ruby, Rails, and the future of programming, Matz described joy, freedom, and motivation as the thing a language gives you that is hard to replicate. Freedom maps cleanly to Autonomy and Drive. Joy turns out to be the Discovery/Play/Joy triad. Motivation is not a force at all, it is the container, and it needs expanding before the mapping closes.
The Contextual Core: Who, What, When, Where
Why is the directive and How is the action, which leaves out the entire middle. Who, What, When, and Where are the locating step: four separate questions, each with its own failure mode, that tell you where you are standing before you move. Splitting them out of the How is what makes the whole model work.
The Meta Structure: How to Read the Three Steps
A high-level map of Why, the four Ws, and How, plus the two properties that make them work: the structure is self-referencing (every step contains the whole shape) and it is a loop (the end of one cycle issues the start of the next). Which also means half the vocabulary is relative to wherever you are currently standing.
The Primary Directive: The Objective Function as Why
Why is not a question, it is the Primary Directive, and it stands alone above the other two steps. What it is, why the general human directive is Explore/Play/Joy, how the specific human directive nests inside the general authentic one, and why Why is answered first and audited last.
Models Are Tools: Portability, Watermarks, and the Work I Want to Keep
A few weeks of running Astra next to Opus 5 left me with three conclusions: the behavior I depend on is mostly harness and habit rather than intelligence, watermarking every output treats a shared piece of work as if the model made it alone, and I want a personal profile that travels with me so the model stops being the thing I have to learn.
There Is No Speedup for Shared Understanding
Six months of building AI infrastructure and coaching coworkers on their agent workflows taught me the bottleneck is no longer code creation. Someone can write ten thousand lines in a day, but nobody found a way to make a colleague understand those ten thousand lines any faster than in 2019. Validation is still the vehicle through which humans actually learn a system, and that work has not been automated.
I Am Often Wrong: The Six-Step System Hiding a Quest Engine
Boris Cherny says he loves being wrong, and lays out a six-step system for how he solves every problem. Underneath the labels, it's three moves repeated twice, and the move he treats as a footnote (Renew) is doing exactly as much work as the one he calls urgent (Drive).