I have been at the same firm for twenty years. Most of that time has been a scale conversation. More offices, more headcount, more assets, more systems, more roadmap than fits in a year. The arc reads as expected: a Back Bay office in the Prudential, then Harvard Square because that's where the energy is. Palo Alto a few years later, signed at 444 High Street after a year of conference rooms and borrowed desks. New York at the Puck Building, then 434 Broadway when the Puck stopped fitting, into 148 Lafayette in a major expansion. San Francisco at South Park, twice, because one office in the city was not the same as one in the Valley. London, DC, Berlin, Bengaluru.
The technology arc tracked the same shape. A Microsoft on-prem stack for the first stretch, Google Workspace from 2016, RIA in 2019, fully remote in March 2020 with zero business disruption, in-house IT by 2022 because the problems had stopped being server rooms. Each of those moves was the right call at the time. None of them is what I think about on a long drive.
What I think about on a long drive is what stayed small.
The first West Coast office was a conference room at Cooley and a desk at the TIFF offices, supported from Cambridge on East Coast hours. Hemant and a handful of people. No ticket queue, no MSP, no architecture review. If something broke, the person who broke it called me, and the person who called me knew my name. Within two years that became 444 High Street and a real office and a permanent presence and all the things that follow. The office was the right outcome. The borrowed conference room is the part I remember.
The infrastructure history of the firm tracks the same shape. The 2016 Google Workspace migration is on every page of the technology story because it earned its place there. It rewired how the firm communicated. It made everything that came after easier. But the migration itself, the part that mattered to me, was small: a sequence of dozens of decisions about which legacy thing got carried forward and which got cut. A list. A discipline. The headline is the cloud. The work is the list.
The validation came in March 2020. COVID closed the offices and the firm went fully remote overnight with zero business disruption. The story everyone tells about that period is the speed of the pivot, but the pivot itself was small. The cloud migration four years earlier had already done the work. By 2020 the firm was running on infrastructure that did not care where anyone was sitting. The headline was COVID. The work was 2016.
The piece I keep coming back to is that the work that holds up is rarely the work that scaled. The on-prem-to-cloud cut held because somebody read the list. The 2020 remote pivot held because the cloud cut held. The 2022 in-house IT decision held because the support model had changed, not because the org chart did. None of those reads as a scale story. All of them are.
This site is the same shape. Cloud Run behind Identity-Aware Proxy on a personal Google Cloud project. A Cloudflare edge in front of it. A honeypot stream in BigQuery, with a redacted dashboard projection in Supabase. A Mac Studio in a closet doing analytics. Static Markdown checked into a Git repo and published as HTML. The whole thing fits in one head, and that is the point. Professional infrastructure is built so it does not depend on any single head. That is what makes it well-built. The personal version is the counterweight. I do not need it to scale. I need it to stay legible to me.
Forty-five is an odd birthday to write about because nothing about the number is structural. Twenty years at one firm is structural. The shape of the work is structural. The number is just the occasion. What I have been thinking through this year is what the small things have actually held. The borrowed conference room. The migration list. The closet Mac Studio.
I do not have a tidy ending for this. The pattern is not a thesis. It is just that the work I think about on long drives is rarely the work that made the page.
It is usually the work that fit in one room.
Part of Notes - recurring short-form on what the work actually looks like.
See also: Hello World, Why I Run Production-Grade Personal Infrastructure.