Consequential initiatives across product, platform, data, and delivery.

ContextThe widget ships inside other people’s marketing pages, where every byte sits on someone else’s critical path and every CSS leak becomes a support ticket.

ProblemA legacy stack was carrying the company’s primary distribution surface, and its cost to the host page had never been weighed against what the product actually needed to do.

JudgmentThe migration was not about TypeScript or React; those were the tools. The question was what the widget costs the host page and how to shrink it without losing capability. Old and new code paths ran side by side through the bulk of the work, so any regression was attributable rather than mysterious. Calendar time spent to buy confidence.

BuildMigrated the widget platform end to end to TypeScript and React, built design-system components shared with the dashboard without dragging styling into the host page, designed cross-domain messaging primitives, and stood up an A/B testing surface the product team could iterate inside without reshipping.

ContextA small team against a noisy data problem: customers were leaving signal across email, Twitter, Zapier flows, and app-store reviews.

ProblemProduct teams could not read any of it without first pretending it was structured.

JudgmentAggregation systems live or die on schema discipline. The most useful work was the least visible: the slow remodel of the data shape so everything downstream could stop apologising for it.

BuildBuilt and maintained the web application end to end, shipped and operated Twitter, email-bot, and Zapier integrations, remodelled 35+ database schemas and the APIs around them, and automated integration testing across CircleCI and AWS CodeDeploy.

ContextThe SDK was the first thing a prospective renter touched. Dashboards, messaging, and the operator surface all depended on it rendering correctly on a property’s marketing page within a second of arrival.

ProblemThe company needed a distribution surface property managers would embed, and install partners needed to integrate it without engineering hand-holding.

JudgmentMake the install easy and the failure modes legible. What the boundary actually promises, and what a host page can and cannot tolerate, became the brief for the TypeScript and React rewrite four years later.

BuildBuilt the flagship widget SDK end to end, reworked setup so install partners could integrate unaided, and added observability that let operators tell whether a property’s widget was healthy.

ContextAn internal engineering organisation with a real client application that teams shipped against daily, and a service mesh assembled from whatever language each team had reached for first.

ProblemNot a greenfield. The client app and twelve-plus services had to keep working for the teams depending on them while they moved.

JudgmentMigrations are mostly about the order you do things in. Get the seams right and the change is boring; get them wrong and every commit is a negotiation. Most of what I know about staged rollouts started here.

BuildMigrated an AngularJS client to React, and contributed to consolidating 12+ microservices onto Mali.js from a mix of Go and Ruby stacks.