The Tech Stack Swiss Army Knife

There's an unspoken rule in tech: pick a lane and be a beast at it. "Frontend or backend? Infrastructure? UI/UX?"

I never quite got that memo being a self taught engineer and honestly, I'm glad I didn't. If you need a label however, Fullstack Software Engineer works, but it's really just the starting point.

☕ The Daily Driver

I write C# and ASP.NET Core at my current job. It has a reputation for being the safe corporate choice. There's something genuinely satisfying about building deep, performant backend architectures with a language that just works at scale. I picked up C# to write an email migration system (from Zimbra to Outlook) and the rest was history. I have come to love it and was the ticket to my current job.

🎨 Frontend Engineering? Yay!

I build user interfaces with Vue/Nuxt. AI-assisted development has changed things for me in that regard. Prototyping is faster, iteration is fun, and the feedback loop is tight enough to actually enjoy the process. I love how simple and cool Vue/Nuxt is, and my go to if I need a user interface for anything I am working on. This entire site is built with Nuxt and Nuxt content. I have also led a few frontend projects. A public example is:

💾 Sysadmin Turned Cloud Architect

Infrastructure is where I truly light up. I didn't come through a lightweight DevOps bootcamp, I started as a classic SysAdmin: bare metal, config files, and the quiet satisfaction of keeping production alive.

Then into the new thing, Containerization, CI/CD and eventually led large-scale architectural migrations, including replacing legacy environments with fully optimized, multi-tenant private cloud infrastructure. I have learnt so much working on premise and architecting private cloud systems so I am starting SwiftInfra with my good friend, read more about our aim and goal here:

🤖 I love Observability

For me, high-fidelity instrumentation isn't an afterthought, it's a foundational pillar of architecture. I am not comfortable if I cannot observe any system. When I'm not managing clusters or debugging backend services, I spend my curiosity exploring the intersection of infrastructure data and AI. I’m constantly experimenting with ways to inject intelligent decoding and automated reasoning into the observability stack, moving past reactive dashboards and static thresholds toward self-healing systems that catch anomalies before they escalate into incidents. Details of that in:

🧠 What Makes Me Tick

I thrive at the inception of hard problems. Complex systems, deliberate chaos, and the grueling process of optimization are where I do my best thinking. I care deeply about clean design patterns, architectural decisions that scale linearly, and understanding why a something works, not just that it works.

If you ever want to discuss distributed systems, debate the hidden trade-offs of on-prem vs. public cloud, or discuss where AI is genuinely shifting developer workflows, let's talk.