back

job4 retro

Silhouette of a person walking with a laptop

2 years and 6 months as a DevOps Engineer.

May 2023 — December 2025.

Photo by Sebastian Schuster on Unsplash

Last updated · 2026-01-27

The role

Cloud infra. CI/CD pipelines. Legacy cleanup. Monitoring and logging.

Predictable load. Stable routine.

I. The Good

What worked.

Growth through legacy

EC2 → Kubernetes. Raw YAML → Helm charts. Tangled Terraform → clean modules.

Fixing old systems is where I sharpened the most.

Stable routine

Work was predictable. Free hours went to learning.

Less stress. Easier to last.

II. Lessons

What broke, what taught.

Tech debt needs time

Legacy was the biggest pain. Fixes never ended.

Most days went to keeping old systems alive — not building. Plan time to pay it down.

MSA in name only

We called it microservices. No service mesh. 40+ ALBs, hand-managed.

More complexity. None of the benefits.

MSA: deploys

True MSA means teams deploy independently.

We approved every deploy. 2–3 hours per engineer, every week. Wrong order broke things.

MSA: no mesh

Devs coded Rate Limiting and Circuit Breakers by hand. Changing a limit = full redeploy.

"We don't need that." "Overkill." Routing, security, costs — all inefficient.

Toil kills motivation

Google SRE book: keep toil under 50%.

We failed. Days, weeks — tickets and deploys. Motivation drained.

III. The Not-So-Good

What hurt.

Politics over tech

Relationships mattered more than good calls.

Safe options won, not best ones. Certain voices always carried — even with bad ideas.

Dust masks at work

Two floors merged to cut costs. Construction during work hours. Masks all day. Noise. Dust.

No concern for people. This was the culture.

What I take away

Culture matters as much as skill.

Software is built by people. Trust and respect beat any tool.

Now.

Two months into job5. The contrast still inspires.

Just don't ask about Friday rush hour in 성수.