How I ended up building things.

The tools have changed. The thing I enjoy hasn’t: understanding how something works and finding a better way to make it work.

Based in London, currently in Technical Operations.

The path so far

Operations · Hong Kong aviation
Six years in live airline operations, where plans meet reality every hour and someone has to own what happens next.
What it gave me
- People
- Timing
- Ownership
- Dependencies
- Exceptions
- Information flow
Data and digital transformation · Moving to the UK
Data analytics led me into digitising paper-heavy luxury-travel operations, and from there into CRM and system implementation.
What it gave me
- Data analytics
- Process digitisation
- CRM
- System implementation
Building · Technical Operations, now
I turn problems I see in day-to-day operations into working systems: internal web apps, live dashboards, contractor administration, reporting, AI-assisted operational tools, and automation workflows.
What it gave me
- Internal web apps
- Live dashboards
- Reporting
- AI-assisted tools
- Automation
What's next
The next chapter is still being written: technical operations combined with solutions-style building, moving gradually towards building and contributing to useful products.

Grouped by the problem they solve. The tools are supporting detail.

Operations
Workflow design, optimisation, requirements, and operational problem-solving.
- Workflow design
- Requirements
- Process improvement
Data
Turning operational data into decisions people can act on.
- SQL
- Data modelling
- Analytics
- Dashboards
- Reporting
Systems and automation
Connecting the tools a team already uses so work moves without retyping.
- APIs
- CRM
- Integrations
- n8n
- Hosting
- Deployment
Building
Getting from an observed problem to a working tool quickly, then making it sturdy.
- AI-assisted development
- Internal tools
- Web apps
- Rapid prototyping

Personal and side projects. Work for employers stays private, so no proprietary data, screenshots, or internal logic appear here.

Built · seeing who else wants one

A wedding-day hub built as a one-day MVP, then iterated for a week while the people running the day updated it together.

Used for real during a Hong Kong wedding.
Shipped in a day, then improved from live feedback rather than guesses.
The original wedding version is complete; whether others want one is the open question.

Building · you are inside it

This site: a public portfolio and life log in front, a private owner-only workspace behind it.

Migrated from a platform-tied prototype to an independently owned stack with every record verified.
Owner-only access with authenticator MFA; database row-level security decides what is public.
Encrypted off-site backups, tested by restoring into an isolated project.
Automated checks run migrations, security policies, and browser journeys on every change.

Built · experiment

A scorer hard-coded for my group’s 港式台灣麻雀 rules, which are messier than they sound.

How my projects have grown: Ambitious UI attempt → Working domain logic → Real operational tool → Full personal system.

I'd like to hear about it.