About This Blog

January 8, 2026

TL;DR: Raw HTML. No framework. I write the words; an AI writes the boilerplate. We're both fine with this arrangement.

Welcome to a blog built the way the web was meant to be built: with an HTML file, a CSS file, and the quiet dignity of someone who has spent 20 years in software and has decided, firmly, not to install another JavaScript framework today.

There is no React. There is no Next.js, no Gatsby, no Astro, no Hugo, no Jekyll, no Eleventy, no "blazing fast static site generator" that requires a PhD to configure and an intern to maintain. There is a <div>. There are several, actually. They are nested, they are classed, and they work.

Now, you might ask: "Sebastian, if you're so principled about simplicity, why don't you type the HTML for each new post yourself?" An excellent question, and one I'd love to answer - right after I explain why I also don't hand-wash my car, manually compile my kernel, or churn my own butter. Some things you delegate. I have made peace with this.

The arrangement is as follows: I write the actual content - the thoughts, the opinions, the occasional embarrassing confession about which implementation I'd have written. A large language model, which I shall not name but which rhymes with "Clod", creates the file, drops in the nav, wires up the paths, and adds the entry to the index. It does this without complaint, which is more than I can say for most CI pipelines.

Is this ironic? A software engineer outsourcing boilerplate HTML to an AI, then writing a blog post about it, which was also published by said AI? Yes. Deeply. I have stared into the abyss and the abyss copy-pasted a <!DOCTYPE html> back at me.

But the words - those are mine. The opinions are mine. The mediocre Python/Qt threading decisions I write about are very much mine. The AI is just the intern I never had, and unlike a real intern, it doesn't ask to leave early on Fridays.

Anyway. That's the blog. Enjoy the posts.