Useful beats impressive.
The best artifact earns a place in somebody's real life.
Away from the org chart
I make things to understand them.
Cars, code, electronics, rooms, gardens, tools, and ideas all become systems once I spend enough time with them. This is the less polished, more personal side of the same engineering mindset.
The connective tissue
The subject changes.
The instinct does not.
I like becoming competent in unfamiliar territory. That usually begins with a real problem, a lot of reading, and the willingness to produce an imperfect first version.
The same habits carry between software and physical work: model the system, expose assumptions, instrument what matters, keep the feedback loop short, and leave the result easier to change than you found it.
What survives the medium
A practical builder's operating system.
Evidence beats posture.
Measure it, run it, drive it, grow it, or put it in somebody's hands.
Make the workings legible.
Durable systems invite repair, revision, and the next useful idea.
01 / Making for others
Useful changes meaning when someone needs it now.
Early in the COVID response, a friend asked whether I could print PPE for his wife, an infectious-disease doctor at a VA clinic whose disposable supply was running dangerously low. That concrete need turned three personal printers into a full-time production line.
The fundraiser brought in $2,360 from 43 donations and was shared 366 times. The work moved from an open-source design to material sourcing, repeatable fabrication, assembly, and finished batches for frontline healthcare workers.
Speed mattered, but consistency mattered just as much. Each revision had to print reliably, use the material efficiently, assemble without guesswork, and move cleanly from the workshop into somebody else's hands. It was a small manufacturing operation built around an immediate human need.
- $2,360
- raised
- 43
- donations
- 11
- campaign updates
- Production / repeatable output
- Storage / completed inventory
- Staging / ready for assembly
- Prototype / fit and assembly
02 / Mechanical systems
A car is a system you can hear arguing with you.
My B5 S4 was never just transportation. It was diagnosis, research, disassembly, tradeoffs, and the particular satisfaction of returning a complicated machine to service.
The interesting work lives between symptoms and root causes: understanding how the whole system behaves before replacing the part that happens to be loudest.
That meant documenting the teardown, organizing dependencies, studying failure patterns, and resisting the temptation to treat each component in isolation. The finished car matters, but the deeper reward is learning enough about the system to make a defensible decision when the evidence is incomplete.
- 01 / Start with the complete system
- 05 / Put the whole system back into service
- 01 / Access the system
- 02 / Open the service position
03 / Physical computing
If the right part does not exist, that is an invitation.
3D printing pulled software, electronics, mechanical design, and patient iteration onto the same workbench. I learned the tools because I wanted the object, then kept learning because each object exposed a better question.
I enjoy functional parts most: enclosures, mounts, organizers, interfaces, and the small custom pieces that make a larger system coherent.
A useful enclosure has to negotiate with the real world: board dimensions, cable paths, heat, mounting points, controls, tolerances, and the order in which a person can assemble it. Every prototype makes those hidden constraints visible and turns the next revision into a more informed one.
- Model
- Plan the physical system
- Wire
- Place the compute layer
04 / Growing systems
Automation is more fun when the output is lunch.
The hydroponics build started with PVC, pumps, cups, and a question about whether I could make a compact growing system work at home. The answer came through successive versions, not a perfect plan.
This is the same systems instinct in a different medium: flow, feedback, constraints, failure modes, maintenance, and an outcome that makes the work tangible.
Plants are unusually honest observability tools. Flow, light, nutrients, spacing, and maintenance all show up in the result. The system improved by watching those signals, changing one constraint at a time, and designing the next version around what daily operation actually required.
- Outcome
- Structure
- Flow
- Assembly
The center
Family is the reason for the work, not material for the website.
Fatherhood shapes what I value: patience, durability, curiosity, and building things that give other people room to grow. That part of my life matters most, so this site keeps it present without turning private lives into public content.
Same builder, different surface