2 min read

Another Corner of the Internet

Another Corner of the Internet
Photo by Gabriel Heinzer / Unsplash

This is not my first corner of the internet.

My first one was a GeoCities site, which probably tells you roughly how old I am. Since then I’ve had plenty of domains, plenty of blogs, and plenty of false starts. WordPress sites, personal pages, half-finished ideas, things that existed for a while and then quietly disappeared.

So this isn’t about novelty. It’s about trying again, but with a different intent.

This time, I’m not chasing an audience. I’m not trying to optimize for anything. I’m not even sure who this is for yet.

What I know is this: I wanted a place to document technical projects and the journey around them. Not just the end results, but the thinking, the mistakes, the tradeoffs, and the parts that usually get edited out.

What changed this time

In the past, my blogs tended to fall apart for the same reasons.

Too much overhead. Too many decisions. Too much pressure to make it “good” instead of just making it exist.

I’d spend more time maintaining the platform than writing on it. Or worse, I’d disappear into tooling and never actually ship anything.

This time, I approached it differently.

I set a few simple constraints and refused to negotiate with myself about them:

  • I own the domain
  • I control the infrastructure
  • Minimal moving parts
  • Nothing that requires constant babysitting
  • Writing should be the easiest part

That’s it.

The setup, briefly

The technical setup is intentionally boring.

A single server. Docker. A reverse proxy that handles TLS automatically. A lightweight publishing platform that gives me a clean editor and mostly stays out of the way.

Getting there was not especially elegant.

There were SSH keys that didn’t work at first. Root versus non-root confusion. Docker permissions. A database that refused to start. DNS propagation anxiety. The usual stuff that happens when you actually build something instead of diagramming it.

At one point I had a site that claimed it was running, immediately followed by an error and shutting itself down. That part was less fun.

Eventually, things lined up. The containers stayed up. TLS just worked. The site responded when it should.

That was the moment I stopped tweaking and took a snapshot. Not because everything was perfect, but because it was stable enough to move on.

What this site is for

This site is a notebook.

It’s a place to document technical projects, experiments, and ideas as they happen. Sometimes that will look like walkthroughs. Sometimes it will look like half-formed thoughts. Sometimes it will just be me writing something down so I don’t lose it.

I’m intentionally not setting expectations beyond that.

This is not a tutorial factory. It’s not a polished portfolio. It’s not a newsletter funnel. It’s a place to think in public and keep track of what I’m learning.

Why now

I’ve learned over time that if I don’t write things down, they disappear. Not because they weren’t important, but because work, life, and noise get in the way.

This is an attempt to slow that down.

Another corner of the internet. Different intent. We’ll see where it goes.

If you’re reading this, welcome.