Where It All Started

I didn’t plan to become a DevOps engineer. Like most people in this field, I stumbled into it — a mix of curiosity, breaking things in production, and spending way too many late nights reading logs.

Over the years I’ve worked across AWS, Kubernetes, and cloud infrastructure. I’ve debugged things that made no sense at 2am, built pipelines that actually worked, and slowly developed a deep appreciation for systems that are boring in the best possible way — stable, predictable, and self-healing.

What I Do

I’m a Platform Engineer. My day to day involves making sure developers can ship code without thinking about infrastructure, keeping systems reliable, and occasionally staring at a Kubernetes cluster wondering why a pod refuses to start.

I work with AWS daily — IAM, EKS, S3, VPC, the whole ecosystem. I’ve learned most of what I know not from courses but from real problems, real incidents, and real consequences.

Why I Started Writing

For a long time I told myself I had nothing worth writing about. Other people were already covering the basics. What could I add?

Then I realised — the most useful content I ever found wasn’t from polished documentation. It was from someone saying “here’s the weird thing I ran into and here’s how I fixed it.” The messy, real, honest stuff.

So that’s what this blog is. No fluff. No tutorials that work perfectly first try. Just real notes from someone working in the trenches every day.

What You’ll Find Here

I’ll be writing about things I actually use and encounter:

  • Kubernetes — the real stuff, not the happy path
  • AWS — architecture, cost, security, the things that catch you off guard
  • Platform engineering — building internal platforms that developers actually want to use
  • AI — I’m currently navigating my way through the AI era, learning as I go and sharing everything along the way

The AI Chapter

This is the part I’m most excited and most honest about. I’m not an AI expert. I’m a Platform Engineer who realises that AI is changing the tools we use, the way we work, and the infrastructure we build on.

So I’m learning. Publicly. One experiment at a time. If you’re on a similar journey I hope this blog becomes a useful companion.

Let’s Go

This is post one. There will be more. Some will be long deep dives, some will be short notes from something I figured out that day.

If any of it helps you — great. If you disagree with something — even better, let’s talk about it.

Welcome to the blog.

— Jana