The Beginning

It started with a broken server at 3 AM.

I was working as a backend developer then, and our production server had gone down. The on-call engineer wasn’t answering. I had to figure it out myself.

That night, I wrote my first automation script. Not because I wanted to be a DevOps engineer. Because I wanted to sleep.

The Turning Point

After that incident, I started noticing how much of my work was repetitive:

  • Deploying the same code to the same servers
  • Manually running tests before releases
  • Copy-pasting configuration between environments
  • Writing the same SSH commands over and over

I wrote scripts to automate all of it. Some were terrible. Some actually worked. The feedback loop was immediate — if the script failed, I knew right away.

The Transition

The shift to full-time DevOps happened gradually:

2020: Wrote bash scripts for everything
2021: Discovered Docker, everything changed
2022: First Kubernetes cluster in production
2023: CI/CD pipelines, infrastructure as code
2024: GitOps, ArgoCD, automated everything
2025: AI-assisted automation
2026: ?

Each step solved a problem I actually had. Not because I was chasing trends, but because manual work was driving me crazy.

What I Learned

Tools change. Principles don’t.

Kubernetes, Terraform, Ansible, GitHub Actions — they’ll all be replaced eventually. But the principle remains: eliminate repetitive work, make failures impossible, ship with confidence.

The best automation is invisible.

When automation works perfectly, nobody notices. That’s the goal.

** humans make mistakes, and that’s okay.**

Automation isn’t about eliminating humans. It’s about removing human error from the parts where it hurts most.

Why I Keep Going

The mission: liberate humans from routine work with AI.

DevOps was my training ground. I’ve seen what happens when humans are buried under repetitive tasks. I’ve felt the relief when a good script handles the boring stuff.

Now I’m focused on the next level: using AI to handle not just the repetitive, but the cognitive overhead too.

The journey continues.