About

I learn by making ideas testable.

I started with software because it made ideas feel reachable. Over time, I wanted those ideas to leave the screen, so I moved toward electronics, sensors, robots, and machine learning systems that have to respond to messy physical inputs.

Right now I am most curious about small autonomous systems, machine learning that touches the physical world, and better ways to measure motion without expensive labs.

Christopher working at a desk with swarm robot prototypes and electronics parts.
A workbench where simulation, solder, sensors, and code meet.

What catches my attention

I notice problems where a simple measurement could change how someone understands a system: a robot finding a path, a pitcher reading their mechanics, or a prototype showing where the assumptions were wrong.

How I build

I like starting small enough to test honestly. Simulation helps me ask the first question, hardware exposes the constraints, and iteration turns both into something I can trust a little more.

Where baseball fits

Baseball keeps the feedback loop concrete. Pitching, teamwork, pressure, and failure all make the same lesson hard to ignore: the next attempt gets better only if I pay attention to what actually happened.