I’m an infrastructure engineer. Twenty years of it, mostly in government technology and security — the unglamorous kind of work where the systems have to keep running and nobody writes a case study about it afterward.
This is where I write things down.
The job here is narrow: be the durable written record for tools whose communities live in places that forget. A good answer posted in Discord at 11pm is gone by morning. A hard-won configuration detail buried in a forum thread is unfindable in a year. If a post here is still useful in eighteen months, it worked.
Where to go
- About — who’s writing, and how these posts are made
- Follow by RSS — the feed, and why it beats a follow button
Posts are on the way. Once a few are up, a Topics index and a Start Here page will join these — both are written and waiting on something to point at.
What this site does not do
There is no analytics on this site. No tracking pixels, no cookies, no fonts loaded from someone else’s CDN, no comment widget phoning home, no newsletter list, no account to create. Your browser talks to my server and to nothing else — and the server is configured to make that break loudly if it ever stops being true.
Server logs keep a truncated IP address for about a day, then delete it. That’s the whole data story. The privacy policy is short now, which is the point.
Notes from the field, not professional advice. Find your own true north.