System Developer at JomJapan, in Kuala Lumpur.
I build the parts nobody thinks about: the portal an agent uses to quote a trip, the page where a customer pays their bill, the rules that decide who sees what. When they work, nobody notices them.
Most of what I touch is money or personal data, so I care more about getting it right than being clever about it.
A landing page for an interior design studio, designed and built to see how far I could push a marketing site: big type, a hero that carries the work, and a projects carousel. The studio is invented and all the content is sample.
A landing page for a renovation contractor: what they do, how it works, and a quote request. Still being built out below the fold.
An expense tracker that keeps everything in your own browser. No account, no server, nothing to leak. Built because most of them want a login before they will let you write down that you bought coffee.
A designer for digital invitation cards, the kind people send for a wedding or an open house. Pick a template, make it yours, send the link. Built on my own time.
Mostly one platform: four apps for a travel agency on a single backend. Agents work in one, travellers in another, staff run the office in the third, and the public sees the fourth.
Where a traveller signs in to see their trip and settle their bill. Money and personal data, so correctness matters more than anything else.
A portal for the travel agents who resell our tours. Leads, quotes, documents and payment, in one place. I have been the main developer since it started.
The public site: packages, group tours, and the booking form. I built the booking flow, the passenger details step, and the group tour picker.
Where people find the Japan tours. The longest running one. Lately I built the appointment booking, so someone can pick a real slot to come and talk to us.
I take on a small number of projects alongside my main work. Usually the kind below, because that is what I build most and I know where it tends to go wrong.
You describe what you want and I take it the whole way: design, build, deploy. Good when there is nobody else to hand it to.
Kad Jemputan Digital and DuitFlow, both built start to finish on my own.
Taking money online without losing track of it. Invoices, deposits, refunds, and the awkward parts: someone closing the tab mid-payment, or paying twice.
A place people sign in to see their own things, and only their own things. Access rules enforced in the data layer, so they hold even if the interface has a bug.
An election data dashboard I built for myself, with its own encrypted data layer.
Marketing sites and landing pages built to load quickly and be found, without a pile of JavaScript getting in the way.
This site scores 99 on Lighthouse and weighs less than one photo.
Often the useful job is not a rebuild. A slow page, a broken checkout, a bug nobody can reproduce. I am happy to be handed a codebase I did not write.
Most of my writing is exactly this: what broke, why, and what I changed.
Not sure if it fits? Tell me the problem rather than the solution and I will say honestly whether I am the right person for it.
Permissions were being read one page at a time. Nobody noticed for a year, because nobody had more than a hundred of them.
ReadIf the only reason a client never sees a number is that the app forgot to ask for it, that is not a boundary. That is a habit.
ReadPrices are stored in the smallest unit, so the number in the database is a hundred times the price. Miss the conversion once and a cheap extra looks expensive.
ReadWhen payment broke in production I did not add a workaround. I traced it to the proxy in front not passing on the original protocol, fixed the check that depended on it, and wrote up what happened so the next person does not lose a day to it.
If the only thing keeping sensitive data out of a response is the app remembering to ask for the safe fields, then one bug leaks it. Permissions belong in the database first. The app filtering stays, but as a second layer, not the only one.
Anything important cannot depend on the customer coming back to the page. Payment confirmation happens server to server, so the order still finishes when their browser does not.
Architecture, data model, auth flow, the bug I just fixed. I keep them in the repo next to the code. It is how I think a problem through, and it is what I hand over when someone else picks it up.
Building the systems a travel agency runs on: leads, quotes, invoices and payments, across four apps sharing one backend.
Worked on Quranirab, a web app for learning Quranic Arabic, building parts of it in Flutter alongside the UI and UX team.
Bachelor's degree, Computer Science
Diploma, Computer Science
Microsoft AI For All (Bersama Malaysia) · Powering The Future 2025
Vue · Nuxt · Next.js · React · Astro · Flutter
Language & StylingTypeScript · Tailwind · Sass
State & BackendPinia · Express · Firebase · Supabase
Motion & TestingMotion · GSAP · Playwright · Vitest
I am not looking for a full-time role, but I do take on projects. If you have something you want built, or something that is broken, send me an email with what you are trying to do.