$ git log --oneline --all
A blog where every article is a living document, tied to a real project.
What This Is
This isn't a blog where posts get published and forgotten. Every article here is tied to one of my personal projects — a homelab rebuild, an automation script that got out of hand, a self-hosted service deployment, whatever I'm currently breaking and fixing.
As the project evolves, the article documenting it evolves too. Updates, pivots, dead ends, breakthroughs — they all get committed, with a full revision history you can browse like git log.
✏️ Living Documentation
Each article is version controlled. You're not reading a snapshot — you're reading a project's entire commit history in narrative form. Every change is tracked, timestamped, and diff-able.
How It Works
When a project changes direction — say I swap Docker for Podman, or rebuild a config from scratch — I update the article and push a new revision. The old version isn't deleted; it's still there in the timeline, right next to the diff showing exactly what changed.
What You'll See on Every Article
That graph above isn't fake — it's the same format every article uses. Click any revision in the timeline and see the article as it existed at that moment. Toggle the diff to see exactly what lines changed between iterations.
Why This Exists
Most tech blogs show you the final, polished solution. They skip the dead ends, the wrong assumptions, the "I tried this first and it failed" parts. Those are the parts that actually teach you something.
By keeping every revision visible, this blog does the opposite — it preserves the struggle. If you're following along with a project and hit the same wall I did, you'll see it in the commit history before I figured out the workaround.
⊞ One Project, One Article
One article = one active project. As long as the project is alive, the article keeps accumulating revisions. When the project stabilizes or ships, the article freezes. New project? New article.
The Git Breadcrumb Trail
Every revision comes with the same metadata you'd expect from a real commit:
commit a1b2c3d
Author: saltthefields
Date: 2026-07-01 09:23
Initial draft: raw notes from the crash
commit e4f5g6h
Author: saltthefields
Date: 2026-07-08 14:30
Add context: packaging everything as Docker containers
You can browse articles the same way you'd browse a repo — oldest commit at the bottom, newest at the top. Click any commit to see the article at that point in time. Check "Show diff from previous" to see the +additions and −deletions between versions.
What This Means for Readers
- Follow the project from start to finish — read the latest revision, then scroll the timeline to see how the thinking evolved.
- Catch the pivots — the diffs between revisions show exactly where I changed my mind and what prompted it.
- See the mistakes too — the wrong turns are preserved. You might learn more from those than the final solution.
⬡ Current Status
This is a living experiment. I'm building it as I go — the blog itself will have its own revision history. Follow me on GitHub for updates, or just browse the articles and watch them evolve.