About Me

I’ve always been more interested in understanding how things actually work than just getting something to function once and moving on.

When I build something, I tend to go a little deeper than just making it work. I want to understand why it works, what could cause it to break, and how it would hold up if it had to scale or handle real pressure.

That mindset carries over into everything I do. I naturally think about systems in terms of tradeoffs, constraints, and how different pieces connect.

My path into tech hasn’t been completely linear. I started in medical training, spent time working in high volume operations, and eventually moved into self studying IT and building projects on my own.

Looking back, there’s been a consistent pattern. I’ve always been drawn to environments where there’s structure, clear expectations, and a sense that what you’re doing actually matters.

I’ve realized I learn best when I can apply something directly, see the result, and understand the impact. That’s what pushed me toward building real projects instead of just focusing on theory.

I tend to notice inefficiencies pretty quickly, especially in systems that people interact with every day. Once I see something that doesn’t make sense, it’s hard for me to ignore it.

A lot of my projects have come from that. Vector is a good example. It started from going through the job application process myself and realizing how repetitive and inefficient it was.

Instead of working around that, I wanted to see if I could design something that made the process smoother and more consistent.

I do my best work when I understand what I’m working toward and can see how my effort connects to an actual outcome.

When something feels real and has a clear purpose, I can stay focused for long periods of time and go pretty deep into it.

On the other hand, I’ve learned that I don’t respond as well to work that feels disconnected from real application or just focused on memorization.

Over time I’ve started to understand that it’s less about discipline and more about being in the right environment.

I usually approach problems by thinking through tradeoffs instead of looking for a single “right” answer.

For example, when working with cloud services, I’m not just asking what to use. I’m thinking about why I would choose one option over another, what I gain from that choice, and what I might be giving up.

I take a similar approach with AI. I don’t treat it as something that just works automatically. I think about how to structure it, where it can fail, and how to make the output more reliable.

I’m working toward building a skill set that allows me to operate at a higher level, where I can design systems, solve meaningful problems, and contribute in more complex environments.

Right now I’m still in that transition phase. I’ve built projects, developed a strong foundation, and learned a lot through doing, but I’m still working on getting my first opportunity in the field.

My goal is to keep improving, keep building, and continue moving toward that next step.