Best DevOps and Engineering Team Books, and the Order to Read Them
Six books on DevOps, continuous delivery and how tech teams work, rated and ranked in the order I would read them, with what to skip in each.
Lessons learned, problems and solutions
Six books on DevOps, continuous delivery and how tech teams work, rated and ranked in the order I would read them, with what to skip in each.
Seven books on clean code, refactoring, legacy code and TDD, rated and ranked in the order I would read them, with what to skip in each.
Six books on Event Sourcing, CQRS and DDD, rated and ranked in the order I would read them, with what to skip in each.
How I built Mes mots, an offline AAC app in Vue 3 for a kid who doesn't talk yet, between motor-memory constraints, data that never leaves the tablet, and a mutation harness that proves the tests actually bite.
Building a truly offline PWA with Vite PWA and Workbox: the forgotten audio file in the cache, the subfolder trap, and how to apply a service worker update without ever interrupting the user.
A second spam comment sailed straight past my captcha, honeypot and rate-limiting. Why those layers only stop lazy bots, and the content-based filter that closes the real gap.
Every 24 hours a script asks a model to sweep the news and return JSON. One morning it ships a two-week-old announcement as verified fact, and the cause is one word of JavaScript.
Blank page for humans, spam for Googlebot, and an antivirus silent on 373 files. Tracing the entry point through eighteen seconds of logs, then making the intrusion impossible to replay.
An LLM invents plausible citations then confirms they're real. The only fix: resolve every source against an external API. A three-filter pipeline.
Wrap at every layer or once at the boundary? Even Dave Cheney changed his mind. The real criterion: the API contract %w creates with the caller.