why software feels
closer to art.
Notes from the after-hours bench — on restraint, reliability, and treating code as a craft. The technical layer of the brand, written in forest green.
one boundary,
drawn well.
On subtracting more than you add — and why the seam between two systems is exactly where the bugs come to live. So I build with as few seams as possible.
read it · 6 min01 def ship(work): 02 work = subtract(work) 03 if simple(work): 04 return work 05 return ship(work) 06 07 # delete more than you add.
the archive
Short essays on building, shipping, and the craft underneath both. New ones land between projects.
Notes from the after-hours bench
What I actually ship between posts, why the Pi never sleeps, and how a side project earns its keep without becoming a second job.
The agent that cleans up after itself
Designing for graceful exit — the part everyone skips. An agent that knows when it's done is worth ten that just keep going.
Why I run things on a Pi
Constraint as a creative tool, not a limitation. A single board forces the decisions that a fat cloud bill lets you avoid.
Code is a creative practice
The thesis behind the whole brand, written down once and for all. Taste is a feature, and it ships alongside everything else.
No surprises
Observability as a form of respect — for whoever reads the code next, and for the version of you debugging it at 2am six months from now.