Make constraints visible
Clear limits produce better technical decisions and fewer surprises.
About · systems, people, recovery
I work across infrastructure, platform engineering, architecture, and disaster recovery. I care about systems that are dependable, understandable, and easier for teams to operate. Outside engineering, I explore product ideas and make music.
I studied Computer Science at BINUS University and developed my experience through DevOps, infrastructure, platform engineering, architecture, and disaster recovery work.
I’m most interested in the point where infrastructure becomes a product: when automation, guardrails, documentation, and a clear interface let other teams move faster without weakening control.
Clear limits produce better technical decisions and fewer surprises.
Automation should encode a sound process, not hide an unclear one.
Failure paths deserve the same attention as the happy path.
Current role, professional experience, core infrastructure stack, education, training, and community work.
Systems are technical. Reliability is also about how people understand and operate them.
Beyond infrastructure
I explore self-service digital products and make music. Both sharpen the same skill: turning ambiguity into structure without losing the human point of the work.