No. 02 — Operating Manual
The Operating Manual.
How I think, decide, and build — the standard operating procedures behind the work, forged in thirteen years of fire service and carried into everything after it.
One method, five environments.
I'm a firefighter and engineer with the Lafayette Fire Department, and a builder the rest of the time — software, automation, dashboards, and the systems that keep a small business running. I invest in real estate, and I read constantly; the library is past three hundred volumes.
I don't think of those as five careers. They're one method in five environments: understand a problem all the way down, then build something so it stays solved.
How the work gets done.
Understand before building
Diagnose the problem all the way down before reaching for a tool. Most bad systems are well-built answers to the wrong question.
Systems over repeated effort
If I've solved it twice by hand, I build the thing that solves it every time after.
Design the failure path first
Assume the worst moment: 3 a.m., bad input, someone in a hurry. Build for that and the easy case takes care of itself.
Small, reversible steps
Ship in increments that can be undone. Big irreversible moves are where the disasters hide.
Document as you build
Knowledge that lives only in my head is a liability. Write it down so it outlives memory.
Evidence over opinion
Measure it, or don't claim it.