Why the devlog became updates
Writing a long devlog entry for every finding across five projects wasn't sustainable, so the effort moved to articles and the devlog became short bullet summaries.
Every project on this site used to have a devlog: a dated, long-form entry for each thing I found, usually a bug. Across five projects that added up to 68 entries in a couple of months, and keeping it going took more time than the projects could spare.
What changed
The devlog is now Updates. Each update is a short, dated list of bullet points summarising what changed on a project. They’re generated with AI from my commits and notes, and I check them before they go up. Every update says so.
The time I was spending on devlog entries now goes into the project articles instead:
- Build it yourself: how to reproduce the build, in order.
- How it works: the system as it stands, and why it’s shaped that way.
- What I learned: the lessons that apply beyond the project.
Why
Those articles are what someone deciding whether to hire me, or work with me, will actually read. A list of dated debugging posts mostly shows that I was busy. An article explaining why the robot’s controller is six lines long and what the hard parts around it were shows whether I understand the thing I built.
Writing
This section is the other half. When a project needs a concept I don’t know well, I write it up to check I understand it, like 2D and 3D rotation matrices for the robot’s IMU.