What I Work With

Since 2018, when a college friend dropped me into a live PPOB codebase on day one. Payment APIs, background workers, transaction flows.

The legacy half of the job: Bukopinet and the Octopus switching core still run on it. Getting them off is my current project.

REST endpoints built for payment partners who read the docs closely and retry aggressively. PayAja's API talks straight to the mobile app.

ORM where it helps, raw SQL where it doesn't. Knowing when to switch is the actual skill.

JWT and OAuth2 flows, hardened over years of fintech integrations and partner audits.

High-volume payment processing where a lost record is not an option: idempotency, reconciliation, audit trails.

Schedulers that run thousands of transaction jobs a day so the operations team doesn't have to.

My first and longest database, since 2018. The one whose query plans misbehave at 2 a.m.

Business logic that lives close to the data, versioned and reviewed like any other code.

The part of the job I enjoy most: reading execution plans and shaving milliseconds off queries that run a million times a day.

The newer half of my database work, since 2021, on e-commerce catalogs and then high-volume financial data.

Keeping big transaction tables queryable by splitting them before they become a problem.

The Qodyra year: UMKM product catalogs — clothes, shoes, everything — modeled as documents because they refuse to fit in rows.

Keeping data honest when it lives in two different kinds of stores at once.

Wiring apps to banks, aggregators, and Xendit — and handling every weird thing they send back.

Bill payments at national scale: electricity, telco, university tuition. My least favorite part is still real — new supplier, huge catalog, every product and fee added to the switching core one by one.

The server side of MiniATM devices — the connection that turned PayAja Bisnis into BayarBayar. Fast responses, tight security, no second chances.

Making sure every rupiah that enters the system can be accounted for on the way out.

The destination of our current re-platform: .NET Framework services rebuilt on .NET Core so they can leave Windows and run in containers.

Moving systems that can't afford downtime: staged cutovers, rollback plans, nervous stakeholders.

Full convert to Claude Code. It does a lot of the typing now; I do the judging.

API documentation partners can actually integrate from, kept in sync with the code.

Azure DevOps from day one at Arranet, repos and boards both — with a Trello era when the license got too expensive. Same discipline, free tier.

Years of working inside a certified quality process: decisions documented before they become mysteries.

Writing specs other engineers can build from without a meeting to decode them.

Where I started in 2014, upgrading bank office PCs. Old habit that still pays off every time production hiccups.

Enough to build this site by hand, which is how it was built.

Vanilla for the front of things: fetch, DOM, no framework unless the job actually needs one.

For internal tools that need to look decent by Friday.

The Qodyra year: an UMKM e-commerce backend with Xendit payments, learned from zero on the job.

Took Bukopinet from web to mobile with it — the app, the API behind it, and the dashboards around it.