Away from the org chart

I make things to understand them.

Cars, code, electronics, rooms, gardens, tools, and ideas all become systems once I spend enough time with them. This is the less polished, more personal side of the same engineering mindset.

Bob's silver B5 Audi S4 viewed from the front three-quarter angle
B5 S4 / A finished machine is only one frame in a much longer systems story.

The subject changes.
The instinct does not.

I like becoming competent in unfamiliar territory. That usually begins with a real problem, a lot of reading, and the willingness to produce an imperfect first version.

The same habits carry between software and physical work: model the system, expose assumptions, instrument what matters, keep the feedback loop short, and leave the result easier to change than you found it.

Personal operating principles

01

Useful beats impressive.

The best artifact earns a place in somebody's real life.

02

Evidence beats posture.

Measure it, run it, drive it, grow it, or put it in somebody's hands.

03

Repair is a design feature.

Durable systems make their own workings legible.

04

Personality can stay.

Optimization should not sand away the reason a thing was worth making.

Family is the reason for the work, not material for the website.

Fatherhood shapes what I value: patience, durability, curiosity, and building things that give other people room to grow. That part of my life matters most, so this site keeps it present without turning private lives into public content.

The garage, the garden, and the codebase all reward the same thing: paying attention.