About Sharon

The arc

Born in Vancouver, raised in Hong Kong from a few months old. Eighteen years in a fast, competitive city, aiming at law. Then back to Vancouver for a political science degree at UBC, where student government, clubs and sport turned out to be the real training: get people aligned, then deliver.

Computer science came next, out of competitiveness and curiosity, and the calling turned out to be one door over in product management. What followed was a deliberate run of adjacent roles, software engineer, business analyst, then product, program and project management, each one adding a piece of the repertoire I use now.

The name

BaoBei 寶貝 is a Mandarin term of endearment, the word for something treasured, the thing you take care of.

That makes it the closest thing I have to a design brief. The lab is named for who the work is for rather than who makes it, and an app only earns the name if I would happily hand it to someone I love.

How I build

A decade of 0→1 launches taught me the part most side projects skip: the operating model. So the lab runs on one: the same discipline, at one-person scale.

Directives, not chat

Every feature is a written brief with scope, edge cases and checkable done-criteria. Anything outside it is commentary.

Design before build

No screen gets built until mockups are reviewed for flow, content and copy, in light and dark, on phone and tablet.

Every build tagged

A tag at the exact archived commit and a plain-language changelog. Learned the hard way, four hours after the first approval.

Deferred work has a trigger

Nothing is "revisit someday"; each item names the condition that forces it. The day the ledger paid out, nine patches closed twenty-two findings.

Gates before release

A six-part audit, schema verification and a physical-device matrix before every archive.