Automating the boring stuff so I can focus on what actually matters.
I'm a DevOps Engineer who can't help but automate everything in sight. My relationship with IT started around the age of 10 β building basic websites, fixing hardware, reinstalling Windows for the whole neighbourhood, messing with routers and home serversβ¦ you know the drill.
That curiosity never went away. These days I design and maintain cloud-native infrastructure β Kubernetes clusters, GitOps pipelines, IaC β and I still spend my personal time tinkering with side projects. Not because I have to, but because IT is genuinely my biggest passion, not just a career.
I'm also keeping a close eye (and hands on keyboard) on the AI space: LLMs, AI-powered tooling, and how all of this is reshaping the way we work in infrastructure and platform engineering. If it's new and interesting, I want to understand it.
- π Β Working as a DevOps Engineer, happy where I am β always open to learning something new
- βοΈ Β Main playground: Google Cloud Platform + Kubernetes
- π€ Β Daily AI tools: GitHub Copilot and Claude β and actively exploring LLMs applied to DevOps workflows
- π Β Security is non-negotiable: WAF, zero trust, hardened configs β I want everything locked down by default
- π§ͺ Β Personal projects: maybe not production-grade, but proof that my terminal is never idle
- π Β Philosophy: automate early, iterate fast, monitor everything β and secure it all
Infrastructure & Orchestration
CI/CD
Cloud
Monitoring & Observability
Scripting, Tools & OS
Security & Networking
π Cloudflare is a personal favourite β WAF rules, DDoS protection, zero trust access, DNS, CDN... I like things locked down and I enjoy every layer of it.
Databases
Version Control & Collaboration
AI Tools & Productivity π€
Shiny tools are great β but they're built on top of things that have been working for decades, and knowing the foundation is what separates someone who uses infrastructure from someone who truly understands it.
Before Kubernetes, there were bare-metal servers. Before Terraform, there were config files edited by hand at 2am. Before GitHub Actions, there was a Jenkins pipeline held together with hope and shell scripts.
I've been through all of that β and I think it shows:
"The cloud is just someone else's Linux box. And I know my way around Linux boxes." π§
Thanks for stopping by! Feel free to explore my repos or reach out π€
Yes, obviously this README was crafted with AI. No, I'm not ashamed β quite the opposite.
Welcome to the 21st century. Adapt or reboot. π€




