Writing
Things I figured out the hard way.
Architecture decisions, tradeoffs I wish someone had explained earlier, and the occasional deep dive into systems that shouldn't work but do.
Running a Web App Inside React Native Without Losing Your Mind
How we built a Dual Runtime System that let a React web app live inside a React Native WebView, with clean contracts, delegated auth, one navigation brain, and a bridge that never leaked chaos.
Building a Sci-Fi Portfolio: Glitch Effects, Lightning, and Retro Terminals
How I built the first version of this site: a glitching name, fractal lightning that inverts the whole screen when it strikes, and terminal-style contact cards. The real effects are running inline, starting with the hero.
In progress
Drafts I'm circling. They land here when they're actually done, not before.
- Why I stopped writing clever codeOn the years I spent optimising and abstracting everything, and what changed when I started writing for the tired version of me at 11pm.drafting
- What black holes taught me about system designEvent horizons, information, and why the best abstractions hide complexity without losing it. Half physics, half engineering, fully indulgent.outlining
- Perceived vs. actual: making things feel fastA field guide to the gap between what's slow and what feels slow, drawn from rebuilding an app users had written off.notes
- The founding-engineer years: what I knew at 23 and later forgotOn building an entire stack alone, at full speed, with nothing to lose, and what that certainty quietly costs you later.someday