Hello, World
Starting a devlog. Why I'm writing, what to expect, and what happens when a developer decides to go public.
I’ve been meaning to start one of these for a while.
Not a “content strategy” blog. Not a personal brand. Just a place to put thoughts down — the same way I keep a sketchbook, or a voice memo folder full of half-finished chord progressions. Something with no audience assumed, no engagement metrics to chase.
Why now
I turned 24 last month. Not a milestone birthday, but it felt like one. I’ve shipped a lot of code over the last few years, whether for clients, for companies, for side projects that never made it anywhere. I’ve realised I remember almost none of it. Not the decisions, not the tradeoffs, not why something worked when the obvious approach didn’t.
This is a memory prosthetic. Also, possibly, a mirror.
What this is
I’m a developer by trade. I make music when I have the evening free. I paint when the coding brain is too fried to do either. All three of these live in separate compartments that occasionally leak into each other in interesting ways.
This is the place where I let them leak.
Expect:
- Written posts — essays, rants, and notes on building things
- Project writeups — deep dives into what I’m working on
- Music and art — process notes and finished pieces
No schedule. No newsletter. Just things.
The stack
The site itself is built with Astro, React, Tailwind, and MDX. Dark by default. Minimal by design. I like it when the tool is invisible.
If you’re reading this and you know me: hi. If you found this some other way: welcome. I hope something here is useful or interesting to you. And if you were wondering, yes, i wrote most of this text with AI. Claude, specifically.
Let’s see what happens.