Sovereignty as an SRE problem.
The political ask is independence. The engineering work is SLA, staffing, complexity, and creating an operational surface for a sovereign operator with a hyperscaler's stack.
Three years on Google Cloud Dedicated / S3NS.
https://t.co/aRxdR8Wsqq
@osidenko_ Yes it's broader. Look for verifiable public work; arguably some legal work/verification in case laws IS public except locked behind (pseudo?) paywalls.
Coding LLMs spread because public code spread.
Production engineering data is private by default, so AI for-ops concentrates around whoever has it.
The data plane matters more than the model.
https://t.co/6FVAlJij1R
LLMs got good at code because it's verifiable: tests pass or fail.
Production engineering isn't. Same change, different outcome depending on live state. No cheap reward signal.
https://t.co/AJvy5dsjFP
A file is a table. A line is a row. `comm -12` is intersection, `comm -23` is set difference, `join` is an inner join, `sort -u` is SELECT DISTINCT.
A small line-oriented relational algebra hiding inside POSIX.
https://t.co/sMKsol2fWz
Fleet automation lesson four years on: the caps on your destructive operations bound count. They don't bound concentration. Sorted host lists correlate with physical topology, and 'head -n 5' will cheerfully take out a rack.
https://t.co/1vLbZQvayB
I spent Q1 2026 interviewing for Staff+ SRE roles at AI infra companies. Both sides using LLMs. No one asked to see my tool setup, or how I decide when to generate code and when not to.
The bar is still Judgement. The interview format hasn't caught up.
https://t.co/LGE0lMdRfT
Most AI takes come from the outside looking in.
Five Crusoe leaders share what they're actually seeing in AI infrastructure right now. An authentic view from inside the machine: https://t.co/TDTYdb9wrL
Given Trumpโs Easter threats to carry out new war crimes in Iran, we should think one or two steps ahead about a coup attempt connected to the war. And then deter it. (1/17)