About

I didn't get into software by building flashy AI products. I got into it by fixing things. Before I wrote code, I worked in IT support, reinstalling operating systems, setting up networks, terminating cables, and getting broken computers running again. A lot of that job was sitting with people who were frustrated because the technology they depended on had failed them at the worst possible moment. That stuck with me. It's where I learned that software isn't really about whether the code runs; it's about whether it actually helps the person on the other side instead of making their day harder That's what pulled me into building software myself. I moved from support into web and backend development, picking up React, JavaScript, Python, FastAPI, and Flask along the way, mostly because I wanted to understand how things work underneath, not just how they look on the surface. Lately I've been drawn to AI engineering: agentic systems, retrieval workflows, and running local models, with an eye on the kind of AI that solves an actual business problem rather than just demoing well. I like work that's useful and clean enough for someone else to follow, whether that's a frontend a person can navigate without thinking, or a backend bug I chase for hours until it finally behaves. Outside of code, I'm interested in digital business and how technology opens up opportunities for people willing to adapt early. Right now I'm focused on becoming an engineer who can connect three things that usually stay separate, solid software, AI systems, and real business value, and on getting a little better at it with every project.