About Me

Hey, I'm Hugo 👋

I'm a 31-year-old infrastructure engineer with a decade of experience in enterprise IT. Over the years, I've built and maintained critical infrastructure for organizations - from network security to cloud architecture to everything in between.

What I've Worked With

If you've dealt with enterprise infrastructure, you know these aren't just bullet points on a resume - they're battle scars. Here's what I've managed hands-on:

Network & Security

  • Palo Alto Networks - Firewall clusters for enterprise security
  • F5 Big IP (LTM/ASM) - Load balancing and application security
  • Cisco Nexus/Catalyst - Switching environments at scale
  • Forcepoint Email Gateway - Email security operations

Cloud & Virtualization

  • Azure Cloud - Virtual Networks, VPN/App Gateways, VNET Peerings, Private Endpoints, Load Balancing, AKS, and more
  • VMware - Virtualization support and maintenance

Systems & Identity

  • Linux & Windows Server - System administration across platforms
  • PKI Management - Internal and public certificate lifecycle
  • Identity Management - WSO2 Identity Server and Okta Workforce Identity
  • SealPath Protection - Data confidentiality and protection

Monitoring & Automation

  • PRTG Network Monitor - Proactive alerting, SNMPv3, Netflow, scripting
  • PowerShell & Bash - Custom scripts for automation, monitoring, scheduled tasks

This isn't everything - just the highlights. Ten years in enterprise infrastructure means you touch a lot of systems, fix a lot of problems, and learn which vendors lie about their "easy setup" process.

In February 2026, I made a decision that scared the hell out of me: I quit my job.

Why I Left

Burnout is real. After years of putting out fires, maintaining systems, and solving the same problems over and over, I realized I was stuck in a loop. I wasn't learning anymore. I wasn't growing. I was just... surviving.

So I decided to hit the reset button. No safety net, no backup plan, just a conviction that there had to be more to life than feeling exhausted and underutilized.

Why This Blog Exists

Infra Struggles is my way of turning 10 years of experience into something useful. If I've learned anything in this field, it's that we all face the same struggles:

  • The cryptic error messages that make no sense
  • The "urgent" production issues at 3 AM
  • The documentation that's either missing or outdated
  • The feeling that everyone else has it figured out (spoiler: they don't)

This blog is my attempt to help someone avoid the mistakes I made, save a few hours of debugging, or just feel less alone when infrastructure goes sideways.

What I'm Doing Now

Figuring it out, honestly. I'm exploring new opportunities, building projects, learning things I never had time for, and documenting it all here. Maybe it turns into something. Maybe it doesn't. Either way, I'm done being stuck.

If you're reading this and you're feeling burnt out, stuck, or wondering if there's more out there - there is. I don't have all the answers, but I'm proof that you can hit the eject button and survive.

Let's Connect

Got questions? Want to share your own infrastructure war stories? Drop me a line. We're all figuring this out together.

Welcome to the struggle. 💪