Why this site exists
Most of my working week goes into presales: sitting across from a CISO or a procurement lead and turning a security architecture into something that survives a budget conversation. It's a job that rewards clarity — the best diagram is the one nobody has to ask a follow-up question about.
This site is the off-the-clock version of that habit. Two things live here:
A journal, for write-ups that don't fit in a client deck — architecture patterns I keep re-explaining, presales lessons that took longer to learn than they should have, or a tool I built over a weekend.
A ledger, because I got tired of a spreadsheet that broke every time I added a column. It's a small, private portfolio tracker: add a holding, update the price, see the gain or loss. It runs entirely in the browser — there's no server behind it and no account to sign into, so nothing about what you hold ever leaves your machine.
Everything on this site is static — hand-written HTML, no database, no backend. That's a deliberate choice for a free host and a small personal project, not a limitation I'm fighting against.
What's next
More notes, as they're worth writing down. If you found this because you're deciding what to build for a similar side project — the honest answer is: start smaller than you think, and let the tool earn its second feature.