Selected Work

What it is

The official iOS and Android app for OGSE Sabah 2026, the Oil and Gas Services and Equipment Conference held 4–6 June 2026 at the Sabah International Convention Centre. PETRONAS, Shell, ConocoPhillips, and regional operators in the energy sector.

Conference schedule

Full programme browsable at a glance. Sessions colour-coded by type: keynotes, panels, workshops, ceremonies. Live indicator showing what's on right now. One-tap bookmarks and direct calendar export.

Networking

Attendee directory with real-time private chat. No phone number exchange, no business cards. Exhibitors get a personal QR code on their profile; scanning it drops you straight into a 1-on-1 chat with them, replacing the traditional booth handshake.

Entry & access

Event entry QR code lives in the app, full-screen and ready to scan at the door. No printed badge, no digging through confirmation emails.

Auth

Passwordless. Email plus a 6-digit OTP. Session persists across restarts.

The constraint

A live, multi-day industry event. Real-time messaging, QR scanning, calendar sync, and attendee access all had to work when the doors opened on June 4. There was no window for post-launch fixes.

The platform

Multi-operator B2B2C booking platform covering tours, attractions, accommodation, and transport across Malaysia. Amazing Borneo has run it for 20 years, serving 500,000+ travellers. UNESCO Global Geopark partner. Endorsed by Visit Malaysia 2026. Live nationally.

The challenge

Extending a running production system from single-state coverage to national scale. Sabah's supplier density, booking patterns, and user acquisition dynamics don't map cleanly to the rest of Malaysia. Every architectural decision has to account for what's already live.

MCP architecture

Building MCP (Model Context Protocol) infrastructure so the platform is addressable by AI agents and LLM interfaces. Most tourism platforms will have to retrofit this later. This one has it built in.

Status

Live nationally. Expansion and AI infrastructure ongoing.

Live at

Client

MIMOS Berhad, Malaysia's national security and ICT R&D institute, under the Ministry of Science, Technology and Innovation.

The brief

Implement Malaysian-origin encryption algorithms, developed by MIMOS, into Bouncy Castle, the open-source cryptography library used by banks, governments, and enterprises in Java and C# applications globally.

What this means

Malaysian government-grade encryption is now available in Bouncy Castle. Porting the algorithm from C to Java meant working through memory model differences, type system constraints, and cryptographic correctness at every step.

Signal

Government-commissioned. Deployed in global infrastructure. Cryptographic code has no tolerance for defects.

Stack

Next.js, Django REST Framework, BNBChain, Tezos

Context

Two engineers: myself and the CEO. I was a full-time student at the time. There were no established web3 authentication patterns to draw from. We launched and held the position as Malaysia's largest NFT marketplace.

What I owned

User authentication architecture, designed from first principles before web3 auth libraries were stable. Twitter API identity verification as the primary trust layer for creator accounts. On day two of launch, a coordinated bot attack hit the platform. I diagnosed it and deployed a fix while the platform was live and under active assault. Search and query optimisation at production scale.

What I'd do differently

I would have pushed harder for Ethereum despite the gas cost argument. The long-term ecosystem depth wasn't on BNBChain. I proposed a two-way transaction sync layer for cross-chain consistency that got deferred. I also suggested XRP as a secondary contract target, which the team didn't pursue. The architecture needed more chain-agnosticism from day one.

Clients

CapitaLand, Epson, Sapura Energy, sgActive, and others across Singapore and Malaysia.

Stack

Python, UiPath, OutSystems

Procurement

End-to-end workflow automation for purchase orders, invoices, and goods receipt notes. Removed manual handoffs from high-volume procurement cycles.

HR automation

A staff benefit proration problem at a major enterprise with S$100B+ in assets and operations across 40+ countries. The logic involved prorating benefits across partial employment periods, variable contract types, and cross-entity payroll structures. Two external vendors had been on it for over a year without shipping. I solved it.

Pattern

Problems that look administrative are usually architecturally harder than they appear. The difficulty is always in the edge cases at scale.