About Me

I have 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 has not been completely linear. I started in medical training, spent time working in high volume operations, and moved into IT through self study, certification work, project building, and hands on support work.

Looking back, there has been a consistent pattern. I have always been drawn to environments where there is structure, clear expectations, and a sense that what you are doing actually matters.

I learn best when I can apply something directly, see the result, and understand the impact. That is what pushed me toward building real projects and into support work where technical decisions affect real users every day.

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

A lot of my projects have come from that. Vector and JobSync both 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 design systems that made the process smoother, more consistent, and less dependent on manual tracking.

I do my best work when I understand what I am 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 have learned that I do not respond as well to work that feels disconnected from real application or just focused on memorization.

Over time I have started to understand that it is 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 am not just asking what to use. I am 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 do not 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 am working toward building a skill set that allows me to operate at a higher level, where I can support users well, design systems, solve meaningful problems, and contribute in more complex environments.

Right now I am applying that foundation as an IT Support Technician in a healthcare environment while continuing to build projects that strengthen my full stack, cloud, networking, and automation skills.

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