Real, working systems I've built and shipped — from a live esports tournament platform and its payment-relay Android app to an ERP for my family's dealership. Most link to the source; the private ones are one message away from a walkthrough.
A live Free Fire tournament platform for the community back home in Nepal, now with its own Android app. Players register squads, hold a points wallet topped up through eSewa and Khalti, challenge each other in Clash Squad for points (mods settle disputed results from screenshots sent in the match chat), find teammates (an AI matcher groups same-language players into a squad every week) and chat with photos and video. Staff run events from a moderator panel that matches each point load to the real payment. Supabase backend with row-level security throughout.
Visit the live site → How the hard parts work ↓The operations system for my family's authorised TVS dealership and multi-brand workshop in Nepal. Job cards with separate repair and prep-cost tracks, bike sales and finance, customer dues (khata), cash book, stock, staff attendance and month-end payroll, a calling desk and a loyalty scheme, with SMS reminders through one aggregator. Years of Excel history (sales, enquiries, workshop retail, AMC) are imported so nothing is lost. Built multi-tenant from day one, so a second business unit can plug into the same core.
Private repo: ask for a walkthrough →An under-30 KB native Android app for the JD Arena staff, with no libraries. It forwards eSewa / Khalti "money received" alerts to a Supabase edge function so mods can approve point loads in seconds, gives the owner one button for every mod and admin tool (opened in Chrome Custom Tabs, so Google sign-in keeps working), and updates itself from private, signed download links.
Part of JD Esports Arena ↑A small Windows tool in C for JD Arena players running Free Fire on a PC emulator. It sets the FPS cap to match the screen, keeps the emulator on the fast cores of newer Intel laptops, and puts everything back when the match ends. It stays on the fair-play side by design: it never touches game or emulator memory and has no macros or aim assist. Updates are checked against a SHA-256 hash before they install.
See the download page →Analyzes instruction-level parallelism by comparing sequential and parallel processing of CPU/GPU-bound tasks — a comprehensive suite covering rendering counts, memory throughput, and multi-threaded execution.
GitHub →A browser-based cybersecurity training game — 15 missions across 3 tiers teaching password hygiene, phishing, 2FA, backups, and post-breach response through short hands-on mini-games instead of reading text. No build step, no backend, installable as a PWA.
GitHub →An inventory and sales system for the family motor showroom: stock, a sales history page, and customer and finance records that only the owner role can read.
Private repo: ask for a walkthrough →The site you're on right now: hand-built, no framework. The hero is my portrait as a 3D sculpture of 28,000 dots that turns its head towards your cursor, made from one photo with an AI cut-out (rembg) and an AI depth map (Depth Anything V2), drawn with WebGL.
GitHub →Players trust this site with real money, so most of the engineering went into making mistakes and cheating difficult.
A phone app forwards "money received" alerts to the backend. A mod can only add points when a player's proof matches one real payment, and each payment can pay only once. Anything unclear goes to the owner.
Payouts run on the server, not in the browser. Only registered squads can be paid, never more than the prize pool, and each squad only once. Every payment is logged, and loads and withdrawals ask for the player's own PIN.
One follow-route card per player and per TikTok account, ever. A database lock stops two mods approving the same account at the same moment, and only approved claims reserve a handle, so nobody can block someone else's.
A scheduled job spots each new TikTok video and alerts every player. Tapping an alert opens the exact page it is about, and the database only accepts video links in one strict format, so a bad row can't send people somewhere else.
The long versions, with file and line references into the real code, including the gaps I haven't closed yet.
Data flow from phone to Postgres, how the wallet stops double spending (row locks, a CHECK constraint, one-time payment references, a scheduled ledger audit), why payments come through a phone relay instead of a merchant API, plus observability, secrets, a threat model and personal-data handling.
Read the design doc →A blameless post-mortem of the 7–8 Nov 2026 outage: one call sent every squad logo as base64, 937 KB on every page open. Timeline from the commits, root cause, what went well and badly, and the rules that came out of it.
Read the post-mortem →I load-tested my jd-ledger wallet API in CI, with transfers fighting over the same hot accounts and duplicate retries. The first run found a real bug: requests queued for database connections inside worker threads, which starved the threads and caused 60-second timeouts. After the fix: 434 requests a second, 0 errors, 0 deadlocks, every duplicate applied exactly once, and 12 of 12 money invariants held.
See the results →