So I Built a Blog. Again.

You ever have that itch to write but nowhere feels right to put it? That's been me for a while now. I've had ideas bouncing around — engineering stuff, AI experiments, even some garden updates — and no real place to put them that felt like mine.

So naturally, instead of picking one of the hundred blogging platforms that already exist, I decided to build one.

I know, I know. "Why not just use WordPress?" or Ghost, or Hugo, or literally any of the battle-tested options that would have had me writing weeks ago. Honestly? Because building the thing sounded more fun than configuring the thing. And if I'm being real, part of the appeal of having a blog is having a project to tinker with between posts. The blog is the side project. The writing is the bonus. I’ll also inevitably break it at some point.

The Platform Under the Platform

I wanted to try out some of Cloudflare's platform and see how it'd go. I've been working with serverless for a while now, so the Workers side of things felt natural — just functions at the edge, nothing too alien. The interesting part has been D1 as the database. It's SQLite under the hood, which is both charming and occasionally quirky. You'll be writing a query and remember "oh right, this isn't Postgres" in the small ways — date handling, some syntax things. But it's been fun to work within those constraints.

The rest of the stack is SvelteKit, which I've been enjoying. Svelte 5 with its runes syntax clicked for me faster than I expected. The whole thing deploys to Cloudflare Pages, and the development loop has been tight — write some code, push, and it's just there.

I'm not going to give you the full architecture rundown here. That's a post for another day, and honestly, the stack is still shifting as I figure out what I actually need versus what I thought I'd need. You know how that goes.

The Meta Part

Here's the funny bit: this post you're reading is being written on the platform it's describing, while that platform is still being built. There are features that don't exist yet. The editor has rough edges. The theme system works but it's not where I want it. And I'm sitting here writing an introduction for a blog that technically doesn't have a second post yet.

It's a little like painting a room while the walls are still drying. But that's also kind of the point. I'd rather start writing now with something imperfect than wait until everything is polished and never actually publish anything. We've all been there — "I'll start the blog when X is ready" — and then X is never ready because you keep finding more things to build first.

So here it is: imperfect, in-progress, and live.

What's Coming

If you stick around, here's roughly what you can expect:

Engineering stuff — deep dives into things I'm building, debugging war stories, tooling I'm experimenting with. Not tutorials where I pretend I knew the answer before I started. More like "here's what I tried, here's what broke, here's what worked."
AI and LLM experiments — I've been spending a lot of time with LLMs, both building with them and thinking about where they actually fit into real workflows versus where they're just hype. Expect some honest takes.
Garden updates — Yeah, the backyard garden is a whole saga. Hogwort invaded my wildflower patch last year and I've been in recovery mode since. If you're into that kind of thing, there'll be posts about it.

That's the plan, anyway. Plans change. But the writing starts now. If any of you have seen me write, just start running :)

#Edge Computing

So I Built a Blog. Again.