I’ve always liked figuring out how things work — whether it’s molecules, circuits, or a Linux server that won’t boot. I got into chemistry because I liked solving problems at the smallest scale, but over time I started to realize how much I enjoyed building things I could actually use. That’s what pulled me toward code.

In grad school, I worked with nanocrystals during the day and spent nights messing with microcontrollers, writing Python scripts, or spinning up servers just to see what I could get working. I ended up building tools for the lab, then small web apps, and eventually full-stack projects that solved real problems I was running into.

These days, I’m focused on building useful stuff — tools that make life easier for other people, whether that’s automating a workflow, managing a rental property, or helping someone understand a tough concept in chemistry. My path into software wasn’t traditional, but it’s given me a practical approach: I’m not just writing code to learn — I’m building things that are useful.