About
I'm an engineer, and rhineware is where I get to build things on my own terms.
For more than fifteen years I've built software in fields where it simply has to work: national-lab science, defense systems, and health tech. That kind of work teaches you the difference between software that's genuinely good and software that merely runs.
rhineware is my own LLC and home for everything else. I build the tools I wish existed, and take on the odd project when it's something I actually want to work on.
Some of what I make is free, some non-profit, some commercial. What ties it together isn't money. It's that I won't put my name on something I'm not proud of.
Why I do this
There's too much bad software in the world. I'd like to leave behind a little more good than I found, if I can help it.
So much of it is overpriced, bloated, dated, or just plain badly made. rhineware is my small attempt at the opposite.
What I value
A few things I try to hold to.
Figure out what actually needs solving before writing a line of code.
Write code someone can pick up later without cursing my name.
I'd rather build one thing that does its job than ten that sort of work.
I look after what I ship. I'm not interested in throwaways.
Background
Neutron & accelerator science
Mission-critical systems
Software and platforms
University of Tennessee
George Washington University
Florida Institute of Technology
The longer version is on LinkedIn.