About this log
I'm an independent developer. I write about backend and automation: the small programs that move files, send mail, check things and keep a home server honest.
- Writes about
- Backend, automation, home servers
- First entry
- Entries so far
- 5
- Pace
- One every six weeks or so
Why a build log
Most of what I build is small and a little boring: a script that runs at night, a page that says whether something is up. Those projects rarely get written about, and the useful part of them is almost never the code. It's the afternoon lost to a time zone, or the backup that quietly skipped a folder.
So each entry follows the same three parts: what I did, what broke, and what's next. The middle part is usually the longest, and that's on purpose.
What you won't find here
- Tutorials that walk through installing things. The tools' own documentation does that better.
- Comparisons or recommendations of products. I mention the tools I used because they're part of the story.
- Ads, sponsored posts, newsletters or tracking of any kind.
Tools that keep coming back
- Gosingle-binary CLIs
- Pythonglue, feeds, sensors
- Bashbackups and cron jobs
- TypeScript on Nodesmall generators
- SQLiteanything that needs to remember
- systemd timersrunning things on schedule
Corrections
If an entry is wrong, I fix it and add a dated note at the end saying what changed. Write to hello@buildlog.vip if you spot something.