Operator, builder, writer, systems thinker.

I work on the messy operational layer where software meets people, vehicles, paperwork, and compliance.

Fire protection is the wedge: a real industry with recurring obligations, real risk, and an operational layer that technology has mostly ignored. The same loop applies anywhere people, vehicles, and paperwork meet: field service, inspections, callouts, and the reporting that keeps businesses compliant.

• Think in systemsEvery part connects to something else. Isolate a component and you lose the behavior of the whole. Think in loops, not lines.
• Prefer useful over cleverClever is cheap. Useful is rare. The best work solves a real problem without ceremony.
• Keep the UI legibleIf the user has to decode the interface, the interface has failed. Clarity is the highest form of respect.
• Build, ship, refineThe loop is the product. Build something, ship it, listen to what it tells you, then make it better. Repeat.
• Own the stackKnow every layer beneath you. When you don't, you're renting someone else's decisions.
• Propose, then actA good proposal beats a fast commit. Think clearly, then move with conviction.
• Move fastSpeed compounds. Hesitation taxes everything downstream. Ship before you're ready, then iterate.
• e/accEffective accelerationism: don't slow down for things that don't matter. Technology moves forward. Move with it.
• inputs > outputsFocus on what you can control. Inputs determine outcomes. Optimize the source, not the symptom.
• 5-lawsQuestion every requirement. Delete what doesn't belong. Simplify what remains. Accelerate the cycle. Automate last. The order matters; most people do it backwards.

• Operational problems that need a builder
• Fire-protection and field-service workflow questions
• Product feedback on anything in the archive
• Introductions to people solving real operations problems

• Anything that needs a certified compliance decision from an AI
• Cold marketing, growth-hacking services, or paid link placement