20+ years of software engineering, accelerated by AI.

Live countdowns and timetables for Hong Kong's ferry network — 16 operators, 69 piers and 87 directional routes, from the Central to outlying-island lines and the Star Ferry harbour crossings down to the rural kai-to services.

A page for every pier pair, an island-hop explorer for chaining islands one sailing at a time, connecting-bus departures enriched with live ETAs, and public-holiday handling applied per individual sailing rather than per route. Trilingual, installable, and it keeps working offline once a route has been visited — which is the state you are actually in, standing on a pier with no signal.

Monetised by a contextual ad engine that targets by route and sailing rather than by who is holding the phone. PDPO-aware and non-behavioural: no profiles, no tracking across sites.

A marketplace connecting independent fitness instructors with students — discovery, booking, scheduling and payments in one place.

The instructors it serves sit in an awkward middle: enough of a following to fill classes, not enough of a business to justify a studio's back office. The software has to carry the scheduling and the money, not just the listing.

Exports every file in an Uploadcare project to your own Google Cloud Storage bucket with the metadata intact — original filenames, upload dates, EXIF, custom fields and virus-scan results.

Exports arrive as 2GB ZIP parts with a manifest in both JSON and CSV, so a migration is something you can check rather than hope about. The usual version of this job is a throwaway script that quietly drops everything the files were carrying.

Built as a product rather than an internal tool: accounts, billing, and a background worker that does the transfer without the browser tab having to stay open.

A portable home for your AI conversations. Import your exports from ChatGPT, Claude and other providers, search across all of them in one place, and export as clean Markdown.

Your conversation history is context you have already paid for — the problem framing, the dead ends, the thing that finally worked. It should not be stranded inside whichever assistant you happened to be using at the time.

Markdown out is the point. It means the archive outlives the tool that made it, and works with whatever you use next.

A campaign site for This is Lantau (就係大嶼), a community radio programme pitched to RTHK's Community Involvement Broadcasting Service. Community backing is part of how RTHK selects programmes, so the page had to do more than explain the idea — it had to give the island somewhere to turn up.

It runs a public vote, then an area poll asking which part of Lantau is yours, weekly prompts, episode threads, written notes and recorded voice notes — all tallied into a visible community pulse. Everything contributed before the deadline is bound into the Lantau Dossier (大嶼提案書) that goes to the selection interview, so taking part is not a gesture: it is literally the submission.

Bilingual throughout, English and 繁體中文. The campaign's own dates — vote closing, dossier sealing, interview — are a single source of truth in code, so the copy, the countdown and the emails change state together instead of being edited by hand on the day.

A custom multilingual WYSIWYG CMS for a Hong Kong hotel — English, Traditional Chinese and Simplified Chinese — with the property's own marketing team publishing directly instead of filing tickets with an agency.

Custom-built, not assembled from WordPress or Joomla plugins. Off-the-shelf platforms are what attackers scan for, because one weakness works across millions of sites at once. This one is not on that list, and has not had a single security incident since launch.

Visitors are geolocated server-side and served the stack that actually works where they are: Baidu maps and analytics, and China-reachable video, for mainland traffic — the Google equivalents everywhere else. Down to converting between coordinate systems, so map pins land on the building rather than a few hundred metres from it.

Next.js optimisation for a high-traffic WordPress publication. Every deployment used to rebuild the site against WordPress — often needing the backend scaled up first — and bots probing article URLs that never existed each triggered a full origin lookup. Serverless was running at 75% of the monthly limit and heading for overage charges.

Delivery moved onto the App Router with Redis KV and Vercel Data Cache, so content survives deploys and missing routes are answered without touching WordPress. 165M requests a month now serve on 4,382 serverless invocations — one function call per 37,000 requests — at an 86% edge cache hit rate.

Builds run 64% faster, 4.19M hostile requests a month are turned away at the edge, and the pre-deploy WordPress scale-ups stopped entirely. The Vercel and AWS bills came down with them.

A verifiable credentials platform. An issuer app lets organisations hand out tamper-proof digital credentials; a wallet app lets people hold and present their own. Decentralised identifiers throughout, including sub-DIDs, so one identity can carry several separable personas.

Credentials are signed with Ed25519 and verify in real time — a holder can prove something without the verifier phoning the issuer, which is the whole point of self-sovereign identity. A public explorer for credential discovery and issuer reputation is in planning, with on-chain anchoring on its roadmap.