All Posts

At TYPO3camp Berlin 2026 I talked about how I run coding agents in parallel across nine repositories with herdr. It is one way of doing it, not the way, and most of what made it work were a few fairly boring rules.

Home Assistant can read calendars from almost anywhere but has no way to push them back out to an external calendar with real create-and-delete sync. Calendar Mirror is the integration I built to close that gap - one-way, automatic, and now working with both Google Calendar and CalDAV.

Home Assistant has no built-in way to say "this entity is expected to go unavailable because its socket is switched off." Labels plus the Spook integration close that gap: disable the dependent devices when the socket goes off, and they drop out of the recorder and the UI for free.

I built the same website — same content, same editorial tasks — in five different content management systems (TYPO3, Strapi, Pimcore, Storyblok, Payload) and gave a talk about it at TYPO3 Developer Days 2026. Slides and live demos are public; here is the writeup.

All three deploy zero-downtime releases with the same releases/current/shared symlink pattern — Capistrano invented it, Deployer and Shippy both cite it as their inspiration. The real differences are the runtime each one needs to deploy, the config format, and what ships built in beyond the deploy itself.