I learned systems from airplanes, small computers, and real customers.

01 / Aviation

The first operating system was a cockpit.

I am a commercial pilot with multi-engine and instrument ratings. Aviation taught me to respect checklists, state, authority, weather, human judgment, and the gap between a clean plan and a real operation.

That background still shapes how I build. The interface must show what is true now. The system must preserve why a person made a decision. The evidence must survive after the moment passes.

02 / Software

I have always used small computers to make the world more legible.

I wrote my first code as a child and kept returning to software through hardware experiments, weather tools, publishing projects, automation work, and product builds. I am most interested in the connective tissue: the part that turns several data sources and human steps into one useful operating surface.

My public work includes aviation displays, radiosonde recovery tools, Raspberry Pi builds, AI-assisted publishing, API products, automation systems, and design tools.

03 / Current work

Today I am building Lightcone Systems.

Lightcone Ledger is operational software for controlled UAS work. It connects the facts, human decisions, and evidence behind a flight release.

I also build and operate a proactive company brain. It prepares context for recurring work, preserves useful findings, and keeps source material close to the analysis.

04 / Outside the current work

The archive is part of the explanation.

The older builds show a long pattern of curiosity across aviation, AI, hardware, education, maps, publishing, and interface design. I keep them visible because a working history says more than a polished list of capabilities.