Louis Fradin
DevRel & Backend Engineer
Louis Fradin is a DevRel and Backend Engineer at Anyshift, where he's helping build the AI context layer for production systems, giving teams the infrastructure graph they need so AI agents can actually understand what's running in prod.
His path to SRE started deep in the stack: four years writing Linux drivers and managing HPC infrastructure for the French Ministry of Armed Forces, followed by three and a half years at Ubisoft building and operating Kubernetes clusters at scale for game servers with Go, Temporal, Talos, or OpenTelemetry.
Today he bridges that engineering background with developer advocacy, advocating for better observability primitives and smarter AI tooling for the people keeping systems alive.
6 Articles
Annie reads Linear now
Forty minutes paging Linear to confirm a returning customer report was the same bug we'd half-shipped a fix for in February. The Linear integration went GA May 13, and Annie pulled both tickets, the linked PR, and the stalled action in twenty-three seconds.
Annie searches Notion now
Ten minutes to find a post-mortem already sitting in Notion. The Notion integration shipped May 12, and Annie picked the same page in eighteen seconds, root cause and open action items tagged.
Annie reads Sentry now
Five tabs to triage one Sentry error. The Sentry integration shipped May 11, and Annie reads Sentry directly now. The first question we asked her returned 67 unresolved errors across four services.
Context Engineering for DevOps interactive conference
How AI agents learn your infrastructure. A walkthrough of the DevOpsCon Amsterdam 2026 talk: the gap between LLMs and production, structural context as a versioned graph, and ACE for self-improvement without labels.
Report Templates: pre-built investigations, one click
Every Monday, the pod-stability review gets rebuilt from scratch. Same dashboards, same correlation work, same write-up. Two hours, gone. Report Templates turn the recurring investigations platform and SRE teams run by hand into one click.
My Workers Stopped Polling: a K8s + Temporal Whodunit
Temporal workflows stuck in Running with zero pollers, and Temporal still reports a healthy task queue. The root cause lives one layer down: a CrashLoopBackOff in the Kubernetes worker pod, caused by a single bad environment variable. A walkthrough of debugging Temporal workers on Kubernetes the manual way (10 minutes), then with an infrastructure context layer that bridges the two systems (seconds).