8 posts
AI & Tools
Agent workflows and tools examined through experiments, worklogs, and practical limits.
Blog
This is one body of work organized into five 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. Tags connect ideas across tracks.
15 posts
Engineering Systems
Architecture, reliability, languages, and the mechanisms behind engineering choices.
16 posts
Field Notes
Personal history, retrospectives, portfolios, and observations from work in progress.
6 posts
Leadership & Teams
Ownership, autonomy, communication, and the systems that shape how teams operate.
18 posts
Quest Engine
The connected framework, from Search, Drive, and Renew to practical applications.
10,000 Hours Was Never Enough
Time matters, but expertise does not come from time alone. In software engineering, AI makes the missing part impossible to ignore: growth comes from new constraints, real feedback, rising stakes, and ownership of outcomes.
Find Your Why: Mastery, Autonomy, and Purpose
Interesting motivation is intrinsic, not extrinsic. Mastery (the pull to get better), Autonomy (ownership and a map of what you control), and Purpose (the why that renews) are the three forces that make work gel. Find your why, and let the Quest Engine help you search for a more interesting one.
Why Search Maps to Mastery, Not Autonomy
There's a natural-sounding intuition that autonomy is about exploring, so maybe it lines up with Search. It turns out backwards, and the reason it's backwards is the most useful thing about the framework: the mapping between Search/Drive/Renew and Mastery/Autonomy/Purpose is fixed by when each force acts, not by what its name sounds like.
Context as Code
Configuration earned its place next to code: versioned, reviewed, owned. The corpus of context that aligns a team (design docs, contextual documents, the why behind the system) deserves the same standard. It's the operating system humans run on, and now the grounding agents read to understand how we work.
Minimize Humans as Glue
Tanya Reilly's 'Being Glue' names the invisible human work that holds a team together but never shows up on your own record. The deeper pattern is the same one behind every high-maintenance system: a person standing in for a fix that was never made. The goal is not to be better glue, it is to build systems that heal themselves so humans are needed as glue as rarely as possible.
Team Identity Ownership
Choosing a name is the first step in taking your team's destiny into your own hands. It is the first thing that creates a sense of belonging, and it is often ignored even though it is such a multiplier. Belonging cannot be dictated. It has to be adopted. It has to be organic.
Language Choice in the LLM Era
A practical guide to choosing programming languages for frontend, CLI, and server development with decision matrices that account for modern LLM-assisted development.
Faith. Guts. Stamina.
In Sing 2, an elderly sheep tells Buster Moon: 'Guts, Stamina, Faith.' The order lands perfectly for the moment. It's not the order the forces operate in. Faith belongs first. Guts follows. Stamina closes the loop.
Context Hunting vs Context Gathering
Why the word 'hunting' matters: context doesn't just lie around waiting to be picked up. Real context requires active investigation, tracing code, chasing state transitions, and turning what you found into something the whole team can use.
Determined. Driven. Consistent.
Tom Brady's Hall of Fame answer was three parts: consistent, determined, and willing to work for it. Most people drop the middle one. That missing piece is why you can be determined and consistent and still be moving in the wrong direction.