October

via Matt Weagle (@mweagle@hachyderm.io): “Mmmmmmmm, others. The ones who have always stood a little bit outside the system. Who could never quite adjust themselves to the right configuration to fit into the workings. Who have always felt a bit out of place. Who look at the systems, all of them, and wonder, Is this really the best we can do? “

Annie Mueller on how the systems we build to serve a goal eventually grow into mutant beasts whose only real purpose is their own survival — until the people no longer serve the goal, they serve the system. The sharpest part is her taxonomy of how people react when a system is threatened: those who can’t see the system as a system fight for it as if reality itself were crumbling, while those who recognize it as a structure imposed on reality are the only ones with the power to change it.

Barry Jones makes a thorough case that story points are unreliable by design: low values imply precision, high values imply ranges, and velocity quietly converts them back into time anyway. Instead of arguing about Fibonacci numbers, he argues teams should measure queues — how long work waits — which gives the business the timeline predictability it actually wanted.

via Alexis Jacomy (@jacomyal@vis.social): Just found out about SiteOne Crawler: https://crawler.siteone.io

SiteOne Crawler is a single dependency-free binary that deep-crawls any site and produces an interactive audit report covering SEO, security headers, accessibility, performance, and broken links. It can also mirror a site for offline use, generate sitemaps, or convert pages to clean Markdown / llms.txt for feeding to an LLM. Available as a desktop GUI or a CLI with roughly 200 options, so it slots nicely into a CI/CD quality gate.

via Rust Weekly 🦀 (@rust_discussions@mastodon.social): Introduction to durable execution with Flawless and Rust

Flawless is a durable execution engine for Rust: workflows that run to completion even when the process is killed mid-flight. Instead of hand-rolling a state machine with resume rules and idempotence guarantees around every external API call, you write plain business logic and let the engine handle the replay. Currently in beta 3.