100 Posts Written
Somehow, this is post number 100.
That feels strange to write.
I did not start this site with a grand content plan. I started it because I wanted somewhere to put notes, project updates, lessons learned, and the occasional opinion that was too long for a social post and too useful to leave buried in a private note.
One hundred posts later, that still feels like the right reason to keep it going.
Not all posts are equal
Looking back through the archive, the posts are uneven in the way a real personal site should be.
Some are proper write-ups. Some are short updates. Some are project notes. Some are reminders to myself after losing time to something I should have written down earlier. Some are reflections on tools, learning, burnout, homelab choices, astronomy projects, 3D printing, GitHub Actions, Raspberry Pis, and whatever else had my attention at the time.
That unevenness used to bother me a bit.
It does not now.
A personal blog does not need every post to be definitive. It needs to be useful enough to return to. It needs to preserve the thinking I had at the time. It needs to give me a place to finish thoughts instead of letting them disappear into chat logs, terminal history, or half-written notes.
Some posts have aged well. Some probably have not. That is fine. The archive is not a polished book. It is a trail.
The quiet value of writing things down
The biggest benefit of the blog has not been traffic, reach, or anything like that.
It has been memory.
When I write about a project, I have to explain what I built, why I built it, and what tradeoffs I made. That forces a bit of clarity. It also leaves future me a starting point.
There have been plenty of times where I have searched my own site because I half-remembered solving something before. A GitHub Actions workflow. A Hugo change. A homelab decision. A Raspberry Pi setup. A note about why I chose one boring tool over a more exciting one.
That is useful in a very ordinary way.
The blog has become part of my working memory.
It also shows the pattern
One hundred posts makes patterns visible.
I keep coming back to the same themes: keep systems understandable, avoid unnecessary complexity, prefer tools that can be repaired, write down the reason behind decisions, and build things that solve a real problem in my own life.
That shows up in the homelab posts. It shows up in the desktop setup posts. It shows up in the way I write about side projects, backups, automation, and learning.
The exact projects change, but the underlying preference does not change much.
I like small systems that are boring enough to trust and flexible enough to grow.
That is probably the clearest thread running through the site.
Writing with less friction
The other thing that changed is the writing process.
Early posts were harder to get out. I would overthink the structure, worry about whether something was worth publishing, and let drafts sit around too long.
Now the bar is simpler:
- did I learn something?
- did I make something?
- did I change my mind about something?
- would writing it down help me or someone else later?
If the answer is yes, it is probably worth a post.
That does not mean every idea gets published. It just means I am less precious about the process. A useful post is better than a perfect draft that never leaves the folder.
Why I am keeping it going
Reaching 100 posts is not a finish line.
If anything, it makes the site feel more worth maintaining. There is enough here now that it has weight. The archive tells a story of what I was working on, what I cared about, and how my thinking changed over time.
I want more of that.
I want the project posts, the build logs, the practical notes, the small lessons, the mistakes, the “this worked better than expected” updates, and the occasional opinion piece when something has been rattling around long enough to deserve a proper shape.
The site has stayed useful because it is not trying to be one thing. It is a notebook with publishing turned on.
That is enough.
One hundred posts is a nice milestone, though.
I am glad I kept writing.