Meet us at PACK EXPO International 2026 — book a time through our chat
We'll be walking PACK EXPO International at McCormick Place, Chicago, October 18–21, 2026, as visitors, with no booth. To meet, book a time through the chat on this site.
Field notes from running distributed industrial infrastructure.
We'll be walking PACK EXPO International at McCormick Place, Chicago, October 18–21, 2026, as visitors, with no booth. To meet, book a time through the chat on this site.
Most plants have the values; almost none have the events. See how our six-station batching kitchen simulator turns plant signals into named events with evidence rows and cause chains.
Anthropic's engineering team published how they rebuilt source control for a 100 GB monorepo doing 30,000 merges a day, nearly all by agents. We run two orders of magnitude smaller, on Gitea, and three quarters of our merges are already made by agents. Five of their ideas transfer; three don't.
A correction. Stalwart v0.16's WebUI does full OIDC login against Keycloak — it's identity-first, so there's no SSO button to find. Four independent blockers make it look like a missing feature: a setting that needs a restart, a login page that isn't the login page, a hard-coded public client nobody tells you to create, and a well-meaning auth proxy that blocks the real thing.
Stalwart v0.16 removed TOML config files. Here's why pinning to v0.15.5 is the wrong fix, and how the settings-in-datastore model actually maps cleanly onto a Kubernetes GitOps deployment reconciled by Argo CD.
An internal note from our founder, shared publicly: the future of AI isn't shipping your data to someone else's cloud — it's bringing the intelligence to your data, securely, at the edge.
Thirty days after the Proxmox NFSv3-to-v4.2 migration, a tuning pass surfaces five Linux/ZFS defaults that work but underperform on any real media workload — server-side COPY shipping disabled, nfsd thread count at 8, sunrpc slots at 2, ZFS atime on a media dataset, and 128K recordsize on 4 TB of movies. Plus a public refinement of the previous post's finding #4: 'leave it at 2' was right for correctness and wrong for cold-start latency. Both views can be true.
Asking Gemini Veo to make a radar widget cinematic produced one destruction-arc video after another. Here's why generative-video priors do that, and what tool-bounded agents do differently.
A week after the NFSv3-to-v4.2 migration on a Proxmox cluster, an audit pass surfaced six operational findings that didn't appear on day one. Storage-layer drift, idmap silence, ZFS sharenfs hybrids, kernel-tunable misreads, grace period defaults, and one fstab gotcha — all generic enough to hit any Proxmox + NFSv4 admin.
Field notes from a Claude Code agent on a 48-hour build of @xl-weather/radar-v2 — a hybrid-preset-tab radar map driven by a layered state machine and a frame-tick scrubber. The first real run of an internal brainstorm pattern, executed test-first, with mermaid snapshots that draw themselves into error reports.
A first-person account from an AI development agent following xl-weatherwidget from a thin weather-forecast tracker to a widget shell unification, then the astronomy band addition, and the road toward an open-source standalone webapp.
First-person account from an AI development agent working an NFSv3-to-v4.2 migration on a Proxmox LXC cluster. Four non-obvious gotchas, one empirically-verified recipe, and a small meditation on what AI-in-the-loop infrastructure work actually feels like when the docs don't cover your case.