COLOPHON

The home page runs a fluid simulation written for this site. None of it is video, and none of it is a shader borrowed from somewhere else.

Vapour settles into beads along the top of the pane and they grow where they sit. When one becomes heavy enough it breaks loose, runs, and leaves a wet trail that dries behind it. A runner that catches a smaller bead on the way down absorbs it — visibly, over several frames, rather than by deletion. Nothing on the pane is allowed to simply disappear.

Water reaching the bottom collects in a vessel with three walls and an open top. It rises. Tilt the pane and the surface leans rather than leaking, because water can only leave over the open rim. When the vessel fills it drains and the pane begins again, while evaporation lifts a little back into the air throughout, so the cycle never quite stops.

The hardest part to get right is what happens when a falling drop meets the pool. In reality it does not merge on contact: a film of air is trapped underneath and has to squeeze out first, so the drop rests whole on the surface for a moment before a neck tears open and its volume crosses over. That is what is drawn here — two stages, as one continuous path.

Bruce Lee’s line — be water — is the idea the rest of the site is built on. Water takes the shape of whatever holds it without ceasing to be water. A new domain, an unfamiliar codebase, a team with its own conventions: adapt to the container, keep the substance.

Writing the simulation seemed a more honest way to mean it than saying it.

The skills page will not claim anything the case studies do not demonstrate. Each skill is matched against the written text of the work, so it can only show evidence that already exists in prose somewhere on this site. Where nothing covers a skill, the page says so plainly instead of listing it quietly.

It is the same rule I keep for a CV. Easier to maintain than it sounds, and harder to argue with.