About Me

Cross-Functional by Design

I'm a technical generalist — not because I couldn't specialize, but because the most interesting problems live at the intersections between disciplines.

Mechanical engineering teaches you to think in forces and constraints. Software development teaches you to think in systems and abstractions. Regulatory work teaches you to think in processes and documentation. Put them together, and you can build things that actually work in the real world.

I've been taking things apart to see how they work since before I could read. Got familiar with A+ certification concepts at 12. Been running Linux as a daily driver for over three years. CCNA-level networking knowledge. Shipped software on Steam. Licensed two federal production facilities. Designed everything from data gloves to rescue tools.

Why Generalists Matter

Startups don't need ten specialists who can't talk to each other. They need people who can see the whole picture — who can write the code, design the part, wire the circuit, and document the process. People who can fill gaps, solve novel problems, and ship.

That's what I do. I connect dots between domains that don't usually talk to each other, and I turn ideas into working systems.

Philosophy

Build things that work. Keep them simple enough to fix. Document them well enough that someone else can maintain them. Ship early, iterate fast, and never stop learning.

I believe in right-to-repair, open standards where possible, and building things that last. I'd rather spend time solving interesting problems than fighting with tools.