AVON - Digital Fashion

Hand me a project and I carry it start to finish, no handoff in the middle. The Avon campaign proves it: I directed the film and built the landing page it ran on.

Most shops split that across two teams and a meeting between them, the film described to whoever builds the page, the page described back to whoever cuts the film. Every handoff is a translation, and every translation drops something. Here the framing and the markup were one decision, made once. Nobody had to explain a cut to a developer, or ask whether a slide would survive a phone.

For Polishop, the product films and the After Effects work that finished them.

Shiseido, where invention would have been the failure

The opposite job: a brand book for Sephora stores, built against a corporate standard that leaves almost nothing open. The task was to read someone else’s rules closely enough to apply them without drifting, page after page, and hand the stores something they could follow. That is closer to engineering than it looks: most code is written inside constraints someone else set, and matching a standard exactly, everywhere it applies, is the same discipline whether it is a brand manual or a codebase.

Why this sits on a developer’s site

I work full stack now: backend, infrastructure, platforms. I grew up inside an advertising agency, where design, photography and video were the job before code was. The taste is not the part that carried. The habit did: keep the fewest people possible between the intent and the thing that ships.