I've been making
complex things feel
simple since I picked
up a guitar.
Took me years to figure out the best players know what NOT to play. The easier it sounds, the harder it was to get there. I've been applying that idea to enterprise software for twenty years.
Where I've done this.
Opinions I'll defend.
The stuff that doesn't fit a resume.
Outside of work, I'm a husband and a dad to two boys, which, honestly, is the most complex systems design challenge I've ever faced. No documentation, constant edge cases, and the feedback loops are deeply non-linear.
I've been playing guitar since 1993. It's the one thing that's been a constant across every chapter, from a kid learning power chords to now deep-diving into tone chasing and signal chains. If there's a piece of gear I haven't read seventeen reviews and three forum threads about, it probably doesn't exist yet.
I bring the same energy to gear research that I bring to work: thorough, opinionated, and endlessly curious. Probably why I ended up in a career where "thinking hard about how things actually work" is the job description.