Software engineer with main interest in software architecture and design. I craft codes that ensure reliability and maintainability.
Side projects I shipped end to end — scoped, designed, built, and put in front of real users.
Mail providers rewrite image and link URLs to route through their own servers, which breaks anything hosted on an internal or VPN-only network. Unproxy restores the original URL at the network layer, before the request leaves the browser.
Hides YouTube's duration, progress bar, most-replayed graph, chapter markers, and storyboard previews, so the page can't spoil a video before you watch it.
A Windows desktop app that pairs a Pomodoro timer with task management — sessions, tasks, and productivity statistics in one place.
An Indonesian tech-insights publication I started in high school and ran for three years before selling it.
Company profile site for an environmental law organisation, delivered solo from UI/UX design through development to production deployment.
Libraries I maintain, and upstream work on the tools I use.
A markup language for pdfmake. Created to solve problem of having to transfer a JavaScript objects, which can contain functions, to a safely markup language that can be decoded later.
Adding dynamic page margins: enable user to write custom margin sizes for each individual page conditially.
A collection of agent skills that helps me (and hopefully others) with engineering and day-to-day stuff. study-codebase turns an unfamiliar repository into a chaptered course with explanations and quizzes; why-and-then-what maps a recurring problem as a causal tree instead of a list of advice.
Three years building backend and distributed systems accross dynamic teams.
Part of the payment team, across a fleet of more than thirty microservices that move real money. My role runs from technical design through to production: I own services end to end, do the design work on the pieces that need it most, and push reliability and observability standards the rest of the team can adopt.
Engineer on the CRM team, on a platform serving thousands of customer support agents worldwide and resolving millions of inquiries and automated jobs a day. I built backend services and the cloud infrastructure under them, and regularly carried features across the whole stack — from designing an API or an LLM pipeline.
I worked inside a cross-functional team of ten, delivering client-facing ERP projects from the UI down to the backend. It was my first taste of shipping to real clients on someone else's deadline.
Hundreds of hours in these pages is why I think the way I do. Pull a volume off the shelf.
The specific language matters far less than the core skills underneath. This is what I reach for most — not a comprehensive list.
{ "focus": ["backend & distributed systems", "payments infrastructure", "software architecture & design", "AI engineering"], "languages": ["Java", "TypeScript", "JavaScript", "Golang", "Python", "C#", "PHP", "SQL", "HTML/CSS"], "frameworks": ["Spring", "Quarkus", "NestJS", "ElysiaJS", "Bun", "Node.js", "React", "Vue.js", ".NET", "Haystack"], "databases": ["PostgreSQL", "MySQL", "MongoDB", "DynamoDB", "Elasticsearch"], "infrastructure": ["AWS", "Alibaba Cloud", "Kubernetes", "Docker", "Rancher", "OpenTelemetry"], "practices": ["microservices", "RESTful APIs", "CI/CD", "observability", "Agile/Scrum", "AI engineering"] }
The greatest engineers do not build perfect systems.They build systems that endure.
Speed is visible today; quality is felt tomorrow.
At the end of the day, the quietest heroes are those who build for a future they may never be thanked for.