Hasbi
Ridwan

I study Management with a concentration in Finance at Universitas Negeri Malang, which is where the finance half of "finance engineer" comes from — AP/AR, reconciliation, and settlement are coursework I actually use.

The ticketing half comes from a real place: I was on the ticketing committee of GKM Odyssey, a campus concert with around 6,000 attendees. My job was booth duty and typing ticket sales into a spreadsheet by hand. It worked, but I watched the same errors happen twice a day — a code typed wrong, a count duplicated, a reconciliation that only agreed at midnight. That experience is the reason every workflow below treats duplicate codes as the main enemy.

The automation itself came after, on my own time: I rebuilt that manual process as n8n pipelines to understand what a structured version would look like. They are personal projects — exploration, not systems the committee runs — but they are built against the real failure modes I saw at the booth.

Earlier still, in high school, I ran a Growtopia reselling operation that peaked at Rp15M/month in revenue. I shut it down on purpose when margins thinned and risk grew — my first lesson in reading unit economics, and why I stopped rather than lost.

Slot sertifikat GKM Taruh file di assets/img/certificate-gkm.jpg — muncul otomatis.

Panitia Ticketing · GKM Odyssey — campus concert, ±6,000 attendees. Booth duty and manual ticket-data entry: the job that motivated everything above.