Read the recap
Most of these started as something I had just finished building and wanted to explain while the details were still fresh. Community meetups, developer conferences, internal sessions for teams I was leading. Different rooms, same reason: explaining it once beats watching the next person work it out from scratch.
Photo
Day-to-day AWS work still means juggling the console, the CLI, and runbooks. At Auditorium BINUS @Alam Sutera, Tangerang, I showed the AWS User Group Indonesia community how the AWS API MCP Server turns that into a conversation: querying and operating infrastructure in plain language, with a clear-eyed look at where it genuinely helps and where it doesn't.
Read the recap →
Photo
DevOps terminology is one of the first roadblocks newcomers hit: lots of terms, all sounding alike, rarely explained. Co-presenting with Wisnu Yumna Y on the Tegal Dev Discord, I broke it down for developers just entering the space: what DevOps actually solves, the terms people mix up, and the core concepts behind them.
Read the recap →SRE principles are usually taught as culture, abstract and hard to act on. For this guest session at RevoU, I took the seven core principles, embracing risk, SLOs, eliminating toil, monitoring, automation, release engineering, and simplicity, and asked a narrower question of each: what does this actually mean for the machines running the system?
Read the recap →Tech stack choices usually get argued on preference. For this internal session at Netmonk, I gave the team a method instead: the external and internal factors worth weighing, an impact/effort priority matrix, and the arithmetic that tells you whether an automation effort actually pays for itself.
Read the recap →A good product is not enough. For this internal sharing at Netmonk, I made the case that you also need a good go-to-market and a good culture, and that when the product is sold to engineers, the engineers themselves become part of how it gets judged.
Read the recap →