About

This is a small revival project. The original blog stopped updating around 2018, then the server went down, then the only thing left was the domain. I liked the writing, so I brought it back.

What this site is

It was a DevOps blog — clear, hands-on, the way the best technical writing is: an engineer working through a problem and writing it down so the next person doesn’t have to start from scratch. Docker, Kubernetes, Terraform, Git, AWS, VPN. I read it years ago and a couple of the posts genuinely saved me an afternoon.

When I checked back recently, the site was gone. Not just stale — gone. Hosting lapsed, database recycled, no backups. The domain was available, the Wayback Machine had snapshots, and the original tone of the blog felt worth preserving, so I started a small project.

How this was rebuilt

Two parts:

• The old posts (everything dated 2017–2018) were pulled from Wayback Machine snapshots, cleaned of archive.org cruft, and re-hosted on a clean stack (Cloudflare Pages, plain static HTML). A handful of images that Wayback never captured are simply missing — those are unrecoverable.
• The new posts (everything dated 2025 onwards) were drafted with an AI assistant, in the same voice and on the same kind of topics — what changed in Kubernetes since 2018, OpenTofu vs Terraform, BuildKit, Tailscale instead of Cisco ASA, and so on. I outlined them, picked the topics, edited the result, and pushed it through several passes. The prose is co-written. The opinions are mine.

Why no byline

I am not the original author and I don’t want to wear their name. The new posts have no byline on purpose — read them as a continuation in style, not in identity. If the original author ever wants the domain or the archive back, both are theirs for the asking.

What this isn’t

It’s not a content farm. There are no ads, no trackers, no comments, no newsletter funnel. The site loads in plain HTML over HTTPS and that’s the whole product. New posts go up when I have something I think is worth writing down — slowly, on no schedule.

If something here is useful to you, good. If something here is wrong, I will quietly fix it.