About Me
I've been obsessed with taking things apart and rebuilding them since I was seven. That obsession turned into a career as a Software Engineer architecting full-stack applications and the infrastructure that runs them. I'm still doing the exact same thing I did as a kid; I just use a tech stack instead of a screwdriver.
My Journey
How it started
I got my hands on our family's Tandy 1000RL when I was seven and immediately started taking it apart. Knowing something worked wasn't enough: I needed to know why. I started programming around ten with StarCraft mods, built my first website at eleven, and never stopped.
What drives me
Same obsession, bigger problems. Today, I architect applications and the systems that run them. I work across the full stack, covering frontend, backend, and infrastructure. When something breaks, I don't slap a band-aid on it. I dig until I understand what went wrong and fix the root cause.
How I think
Engineering isn't my job: it's how my brain works. Whether it is debugging a distributed system, building a mechanical keyboard, or learning a new framework at 2 AM because I can't sleep, the process is the same. I take it apart, understand how each piece works, and rebuild it better.
Why I do this
I build because I have to. Not because someone's paying me or because it's on a roadmap. I do it because there's a problem that needs solving and I can't let it go until I figure out why it exists and how to fix it. That's it.