Afif — Cloud Engineer · 10 years in production
I tinker on cloud and manage foundation people can build on.
Lead a cloud engineering team. Ten years in Cloud Service Provider.
Engineering teams run on writing. This is mine. Share the human knowledge that AI cannot produce. Yet.
1 min read
Should i write in Bahasa Indonesia or English?
I'm originally from Indonesia. I can write in English, but my spoken English is very limited. I'll ask Claude to add a feature that displays both the original text and the English translation.
This is me, if I had been born in the 80s. Maybe.
Ten years, six major versions. Every release is still running somewhere in the stack.
v6.0
v5.0
Cloud infrastructure that is secure, observable and easy to reason about.
v4.0
[What changed in this release, one line]
v3.0
[What changed in this release, one line]
v2.0
[What changed in this release, one line]
v1.0
Initial release. Tickets, logs and a lot of patience.
Most of my job is keeping things from breaking at , and fixing them calmly when they do. I'd rather write a clear runbook than be the one person who knows how it works. If I've done it right, you never hear about it.
The objectives I hold myself to. This is what a team gets when it hires me.
SLO-01
Good infrastructure is quiet. If I've done it right, you never hear about it.
Target
You never hear about it
SLO-02
I'd rather write a clear runbook than be the one person who knows how it works.
Target
Bus factor > 1
SLO-03
Incidents are handled calmly and without blame: fix it first, then fix why it happened.
Target
Blameless, always
SLO-04
Design reviews and mentoring until teammates are better at this than I am.
Target
Team > me
Working remotely
Written-first: decisions, runbooks and handovers live in docs
Async by default, real-time when it matters
[Hours of overlap you can offer]