Writing
Why I Built an HQ Instead of a Portfolio
Portfolios are snapshots. Headquarters are alive. Notes on building a home for everything I make.
- career
- meta
- writing
A portfolio says: here is what I did. A headquarters says: here is what I'm doing.
The difference sounds cosmetic. It isn't. A portfolio is optimized for a single moment, the job application, and goes stale the day after you ship it. An HQ is a system with an update loop: projects land here, research notes accumulate here, half-formed ideas get promoted into essays here.
The rules I set for this place
- Everything connects. A research note should link to the project it fed. A project should link to the lessons it produced. Knowledge that doesn't connect is trivia.
- The Now page is load-bearing. If it's stale, the whole premise collapses. Updating it monthly is the minimum viable heartbeat.
- Ship notes, not just conclusions. The polished essay is the export format. The lab is where the actual thinking happens, and it's allowed to be unfinished.
What I'm optimizing for
Not traffic. Legibility. When a recruiter, a founder, or a future collaborator lands here, they should understand in ninety seconds what I build, how I think, and where I'm headed.
That's the whole design brief. Everything else is typography.