Building,thinking,writing it down.
Experiments that make the work smoother, and things I've worked out along the way.
All posts
-
[Performance] Building a virtual team system
People are hard to change, so I replaced the parts that ran on goodwill with rules, and a few sessions now work like one team. Four rules, five review stages, the pitfalls I hit, and the limits that are still there.
👁 0 ・ ♡ 0 -
[Process] What "done" means for a Scrum task
Fix what review finds on the spot instead of filing more tasks.
Architecture Evolution · Series👁 0 ・ ♡ 0 -
[Verification] The build kept passing while the renderer was already broken
A passing check does not mean it covered what you assumed it checked.
Architecture Evolution · Series👁 0 ・ ♡ 0 -
[Performance] Why does an AI chat's context fill up so fast?
Tackling the task data that gets auto-loaded, so every new chat reads a little less.
Architecture Evolution · Series👁 0 ・ ♡ 0 -
[Performance] Hermione Wasn't Faster: She Was in Two Places at Once
Using the Time-Turner, the blackboard, and the Pensieve as a skeleton, a record of the real pitfalls in turning a solo workflow into parallel Claude Code sessions, including one collision git's own mechanisms never caught, and how the bottleneck turned out to be my own review capacity.
👁 0 ・ ♡ 0 -
What an Interview Can't Measure, Put Somewhere Visible
A one-hour interview can't measure years of accumulated work. My fix isn't complaining about the system — it's putting the work where anyone can see it.
👁 0 ・ ♡ 0 -
Why the site looks like this
The broad strokes are personal taste; the technical decisions underneath are what's worth writing about.
👁 0 ・ ♡ 0