We test application code religiously. Unit tests, integration tests, E2E tests. CI won't pass without 80% coverage.

Infrastructure code? "Just run terraform plan and eyeball it."

That inconsistency is where production incidents are born.

Your infrastructure was deployed with Terraform. It's version-controlled. It's reviewed. It's compliant.

Then someone SSH'd into a server and changed a config file. Someone used the Azure portal to add a firewall rule. Someone ran kubectl edit to patch a deployment in production.

Now your Terraform state says one thing. Reality says another. That gap is configuration drift — and it's the silent killer of reliable infrastructure.

"We follow Zero Trust principles."

I hear this in every security architecture review. But when I ask "show me," the reality is usually a VPN, some network segmentation, and hope.

Zero Trust isn't a product you buy. It's an architecture you build. Here's what it actually looks like when implemented on Azure.

Helm is the de facto package manager for Kubernetes. It's powerful, widely adopted, and the first tool most teams reach for.

It's also overused, over-complicated, and sometimes the wrong tool entirely.

I've been on both sides — applying to hundreds of jobs and getting silence, and having recruiters reach out with relevant opportunities. The difference wasn't my skills. It was my visibility.

If you're a mid-senior engineer still applying through job portals, you're playing the wrong game.

"We're multi-cloud." In most organisations, this really means "we use AWS for some things and Azure for others, and nobody has a unified view of either."

True multi-cloud at enterprise scale is hard. Here's what I learned doing it — and what I'd do differently.

3 AM. PagerDuty fires. You open the runbook. It says:

"Check the logs and restart if necessary."

That's not a runbook. That's a suggestion. And at 3 AM, it's useless.

Here's how to write runbooks that actually help during incidents.

Looking back at 2025, something shifted. Platform engineering went from "that thing Spotify does" to "that thing every enterprise is trying to do." Here's what changed and what it means for 2026.