Why The Site?

I've always been interested in many topics, but not so interested in sharing my thoughts online. I used to believe that a finished product or service was the only thing worth sharing, and those outputs were how I'd communicate insights gained from whatever I was consuming.

When my work and curiousity revolved around building software, insights crystallised themselves through practice. Now that I run (and code) a B2B SaaS while leading growth for a consumer brownie bakery, I'd like somewhere to capture transferrable insights before they get lost between context switches.

How I Chose The Stack

I've been building on top of LLMs for 3 years now. The prototype for AdScribe was built on GPT-3. I went from managing a team of outsourced devs as CTO to running a fleet of agents as my dev team. Before choosing a stack for this website, I noted the following predictions of mine about the future of building software:

1. Frameworks are no longer a requirement. As the maintenance cost of software tends to 0, an emergent fluid framework is fine (aka no framework).
2. Personal software will be ubiqiutous. A custom tool I built won't feel as shiny as it once did, so it doesn't need to stand out. If I'm going to have lots of bespoke software, I would like to have continuity between interfaces across tools and my operating (eco)system. I have my own flavour of Apple's liquid glass design system I use across projects. I also happen to really like liquid glass, one of the few things today that look like the future.
3. Software will have way less dependencies. Non-optional tooling such as runtimes (for now) will be more ambitious. (e.g this project uses Bun's markdown renderer).
4. The JavaScript runtime I'm most bullish on is Bun. I was a Deno fan but their decision to not be backwards compatible burned them. Bun's momentum never stopped, and now they're owned by Anthropic who are likely to IPO at $2T. Bun is here to stay and benefits from a generous supply of frontier tokens.

How This Site Works

This site is built with a single Bun script. Pages use basic JS functions with string interpolation for (escaped) HTML templates, statically rendered. The image sampling for blur effects and colour samping for card backdrops is done at build-time using sips to manipulate images locally and in JS. LLM of choice was Claude Opus 5.5 with Claude Code as the harness.

I use the View-Transition-API for continuity. I actually like animated, fluid UI unlike a lot of devs today. Provided the animations are not aggravatingly slow, of course. Eyes didn't evolve to track non-linear motion, animation can be a good thing actually!

The Feed is a simple markdown list, with format - YYYY-MM-DD - {Description}. Tags are applied via Frontmatter, conveniently supported through Bun's YAML parsing.

The site is hosted on Clouldflare Pages because it's cheap. I also think Cloudflare are on track to be the winnnig neocloud of this era.

And that's mostly it, I have a design system skill I personally maintain and use across projects for continuity with Apple's operating systems. I might open source it someday.

What I'm Interested In At The Moment

Right now I'm interested in growth-hacking (surprise) and doing it sustainably.