I’m an Army veteran and respiratory therapist, but at heart I’m a tinkerer.

I like figuring out how things work, why they stopped working, how to fix them, and whether I can make them do something they were never intended to do.

I’ve been doing this all my life—starting with Tonka trucks and an Erector Set in the ’70s, then BASIC, FORTRAN, and COBOL in the late ’80s; HTML and PHP in the ’90s; CSS, Linux, and Java in the 2000s; and now contemporary tools, methods, and languages.

My only formal training was in the ’80s. Everything since has been self-taught.

Most of what I work on lives somewhere between software, hardware, networking, fabrication, and “I wonder…”

• Linux and self-hosted systems
• Raspberry Pi and small-form-factor hardware
• Networking and home infrastructure
• Web apps and local-first tools
• Automation and appliance-style systems
• 3D printing and fabrication, including wood and metal
• Gaming and streaming technology
• Making old things useful again
• Making complicated systems easier for normal people to use

My projects usually start with:

“There ought to be a way to…” “I wonder what would happen if I…” “I don’t like how this functionality is packaged. How do I…”

Then I start pulling on the thread.

I prefer things that are:

• Useful before flashy
• Understandable before clever
• Repairable instead of disposable
• Reliable in the real world
• Built to be used and abused, not just demonstrated

I’m perfectly happy mixing technologies when the problem calls for it. If a project needs some TypeScript, Go, Linux, SQLite, networking, shell scripts, plywood, and a 3D-printed bracket on a welded platform, that sounds like a pretty good afternoon.

These change depending on whatever rabbit hole I’m currently in, but lately:

Linux · TypeScript · Go · SQLite · HTML/CSS · Raspberry Pi · Docker · Git · Networking · 3D Printing

I’m less interested in collecting technologies than in finding the right combination to make something work.

You’ll find a mix of:

• software projects
• hardware-backed tools
• self-hosted services
• experimental interfaces
• servers and infrastructure
• prototypes
• utilities
• and probably a few things that are difficult to categorize

Some are polished. Some are experiments. Some exist because I got annoyed that the thing I wanted didn’t already exist.

That’s usually where the interesting ones start.

⸻

Current operating philosophy: See a need. Fill a need. Build it. Break it. Figure out why. Make it better.

Occasionally held together with zip ties.