What happens after hour forty?

I have worked in software for over a decade and have worn most of the hats along the way: application developer, DevOps and cloud infrastructure engineer, site reliability engineer, edge and IoT solutions. My day job today is edge computing. My evenings mostly go to agentic development, and what I learn building with coding agents at night tends to show up in how I work during the day.

I have a full-time job and a family, so free time is scarce and projects have to earn it. The ones that do usually involve something I can put my hands on: a desktop robot given a narrow job, or a hook that reviews a coding agent's every turn. There are also robots in various states of completion and a couple of 3D-printed arms still waiting for their purpose. I am at peace with that. Most of what I know, I learned by making something, and this site is the record of what each build taught me.

Mostly build logs, published when a project reaches a point worth writing down. There is no schedule. Each post tries to keep the choices, the dead ends, and the parts that did not work next to the parts that did, so the lesson is there even when the project is not finished.