About Me

I work on infrastructure that needs to be practical, observable, and maintainable. I spend a lot of time learning by building: deployments, routing, storage, monitoring, and other systems work that helps me understand the details instead of relying on defaults.

My work has been shaped by hands-on experience with AWS, automation, and a small homelab. I like working through the parts that are easy to skip in tutorials: resource limits, service exposure, secrets handling, and the debugging that comes after the first deployment works.

My Approach

• I prefer systems that are easy to reason about and easy to operate. That usually means clear configuration, sensible defaults, and enough observability to know what is happening.

• I care about the trade-offs between reliability, complexity, and maintenance cost. I would rather keep a setup understandable than add layers of abstraction that make day-to-day work harder.

• I learn by testing things in real environments. That is why I keep a homelab where I can try deployments, GitOps workflows, and platform concepts without pretending the setup is production-ready.