About · Curiosities

Technical curiosity, in practice.

The professional record lives on the other pages. This page covers how I work, and what I build, test, and take apart on my own time.

How I work

Start from the decision, work back to the test.

I start from the decision someone has to make, then work backward to the test that would actually inform it. Run the system far enough to see where its behavior changes, keep the conditions honest, and document the method well enough that someone else could repeat it or refute it.

I would rather have an independent check than a confident assertion. That includes my own.

Technical curiosities

Areas of active curiosity.

Electronics and embedded systems

Bench projects and small boards: the shortest path from an idea to a working prototype, and the fastest way to find a design error.

Computer vision

Making cameras state what they can and cannot see: partial views, difficult light, moving platforms.

Fabrication and CAD

If a part does not exist, draw it and make it. Most of my test apparatus started as a sketch.

Aviation and flight

Small UAS and the systems around them: flight behavior, airspace, and failure modes.

Local AI and automation

Models and tooling that run on my own hardware, doing useful work under my own observation.

Release engineering

Software that can prove what it installed: build, verify, install, uninstall.

Bench electronics
Fabrication and CAD
Workshop builds
Flight hardware

Kept off this page by design: credentials, client details, private infrastructure, and other people's information.

For the professional record, start with the NIST chapter.