Bearing
About
Three careers. One throughline: systems people depend on.
I advised technology strategy at Gartner. Then I was
commissioned in the United States Navy as an
Information Professional Officer in Information
Warfare, accountable for the networks and communications a fleet relies
on when nothing else is working. Both roles came down to the same thing:
know a system well enough to be trusted with it when being wrong carries
a cost.
I am also a formerly incarcerated engineer. That shows up in the work
rather than around it. Pathfinder exists because reentry is a routing
problem nobody bothered to solve properly. Proper Form was written for a
man preparing for his first interview in years.
The craft is where I spend. Row-level security before the first user.
Test-first on the temporal engine, because time zones punish confidence.
A deterministic fallback in That's Extra, because a demo that depends on
someone else's uptime is not a demo. A recovery drill in Pathfinder's CI,
because a product about someone's reentry cannot be the thing that fails
them.
Everything on this chart is live. Every link resolves. I can defend any
decision on it, including the ones I would make differently now.