🧑💻 Staff Engineer @clever_cloud 🤩 Distributed and Database Systems 🚀 Co-leader @finistdevs 💪 Squash player
Brest, France
Joined February 2009
- Tweets21.5K
- Following4.1K
- Followers3.4K
- Likes18.6K
Pinned Tweet
✍️ I just published "Best resources to learn about data and distributed systems"
Happy learning 😊
#data #distributedsystem
pierrezemb.fr/posts/distsys-…
Pierre Zemb retweeted
1/4 etcd (@etcdio) is the data store behind Kubernetes. We wrote 157 properties it must always satisfy, from its docs, comments and code. Then we searched for runs that break them. Three high-impact issues: one disclosed privately, two below.
cc @serathius @CloudNativeFdn
Pierre Zemb retweeted
Introducing Kimi K3.1 Pro: our most capable 3T-class open-weight model.
🔹 1M-token context, 2.8T total / 104B active params (MoE), Multimodal.
🔹 Full-project coding: games in Unreal, Unity & Godot.
🔹 Excels at parametric 3D modeling in Blender & CAD.
🔹 More reliable at finance work: Accurate modeling with hallucination down by 65%.
🔹 Matching the strongest proprietary models across coding, agentic and knowledge benchmarks.
Kimi K3.1 Pro and K3.1 Pro Highspeed (2–3× faster) are now live on Kimi.ai, Kimi Work, Kimi Code, and the Kimi API.
Open weights by Nov 4, 2026.
🔗 API: platform.kimi.ai
🔗 Tech blog: kimi.ai/blog/kimi-k3-1-pro
Pierre Zemb retweeted
Here's another example, in etcd this time.
Overload causes followers to be marked unreachable, which causes the whole queue of work to be resent.
In other words, overload causes a condition that triggers more load!
Pierre Zemb retweeted
We're donating Agent Skills to the Agentic AI Foundation (@AgenticAIFdn), the same foundation we donated MCP to.
Since December 2025, 70+ agent platforms have integrated the standard, including ChatGPT, Cursor, GitHub Copilot, and VS Code.
Here's what that means for you:
Pierre Zemb retweeted
Yes. See, e.g. how we found critical safety and liveness bugs in every (formally verified) Raft implementation we’ve ever looked at. antithesis.com/blog/2026/fin…
Pierre Zemb retweeted
end-to-end testing > unit tests, in the vibecoding era.
A massive, almost entirely agent-coded refactor passed all unit and pre-merge tests but broke a critical feature.
It was only caught due to my own excessive paranoia making me run end-to-end tests before the prod deploy.
Pierre Zemb retweeted
Revolut has been having an incident for 7+ hours and counting, globally. Some of my friends and family have been pinging me about not being able to make transfers.
An outage when you can't move money is bad for any bank (it's not as bad as losing money ofc!)
This is v bad
Pierre Zemb retweeted
Revolut status page: revolut.com/system-status/
Google Cloud incident: status.cloud.google.com/inci…
It's a single zone outage, one that is textbook to be expected (power loss)
Pierre Zemb retweeted
Si vous avez téléchargé aujourd'hui la dernière version de CLI d'OVHcloud, merci de la mettre à jour à nouveau très rapidement. Sinon effacer. Il s'agit de repo:
github.com/ovh/ovhcloud-cli
La version CLI de 14h47 a été compromise par un hacker. Nous l'avons détecté et bloqué à 16h21. Merci au client qui nous a remonté le souci. La version compromise est v0.11.0 v0.12.0 v0.13.0 v0.14.0 v0.15.0.
La version v0.10.0 et la future 0.16.0 est clean.
On vient de finit les premières vérifications et aucun autre repo n'est affecté. Nous avons aussi retracé l'incident. Le hacker a utilisé le compte github d'un des développeurs et a ajouté un binaire dont le job est récupérer les secrets sur le disque. La qualité du binaire est médiocre mais il peut aller jusqu'au bout. Si vous êtes concernés, merci de changer tous les secrets sur votre disque.
On continue les recherches sur le binaire et on va publier les détails additionnels sous peu.
Pierre Zemb retweeted
I could not imagine being productive without Claude Code Review. It runs on all of my PRs, and catches almost every bug before it goes it. This is a piece of the secret sauce that lets the team and I move so quickly while raising the quality bar
Pierre Zemb retweeted
Cindy is one of the best distributed systems engineers I know, and resistant to any and all hype (also a great writer!)
From her:
"Claude (when given proper instructions, constraints, and context) now writes better code than me, almost always."
Pierre Zemb retweeted
« Avant, la donnée n'avait pas de valeur, elle n’était pas interprétable. » Vous ne lirez sans doute rien de plus idiot aujourd'hui 😆 Mais c'est bien tenté.
Suite de la polémique Withings : j'ai interviewé le responsable de l'application hier. L'entretien est sur Numerama.
👉 numerama.com/tech/2353527-la…
Withings assume sa décision et indique que le principal déclencheur est l'IA : « Avant, la donnée n'avait pas de valeur, elle n’était pas interprétable. »
Withings veut s'imposer comme « la super app de santé en Europe » et pense que l'abonnement est indispensable pour ça. C'est un changement de modèle économique pour les nouveaux clients, potentiellement avec des produits moins chers à l'avenir.
Pas de changement prévu pour les anciens clients, qui ont acheté des produits dans l'ancien modèle économique.
Pierre Zemb retweeted
Muse Spark Open -- weights releasing today -- runs great on new Mac Studios thanks to work with @johnternus and Apple.
Pierre Zemb retweeted
ICYMI: For the 10th anniversary of "Site Reliability Engineering", we’ve rewritten the definitive Google SRE book! 📖
Featuring brand-new guidance on SRE for the agentic era, modern SLOs, and culture.
Get your copy today: goo.gle/SREbook
Pierre Zemb retweeted
agents are really good at generating code
they're not good at generating the right code
they generate too much code and seldom delete code
you can fix it with abstractions, feedback, and architecture
put them in boxes that make bad code impossible
then win-win-win
Zero-downtime Postgres upgrades with logical replication tapoueh.org/blog/2026/10/zer…
Pierre Zemb retweeted
very excited to see this out of A\
this is our thesis at @erscio ! But we are building a git compatibility layer: ersc.io/blog/what-comes-afte…
enterprise adoption of new source control is a big ask, so making a smooth bridge from the past to the future is a big part of our offer
New on our Engineering blog: Creating in-house source control.
In May, we merged around 2,500 code changes per day. In September, we merged more than 30,000 per day. As a result, we became bottlenecked by developer infrastructure built for human (rather than agent) scale.
Here, we share how we built a new version control system—and fully migrated our monorepo from git—in five months: anthropic.com/engineering/re…
Pierre Zemb retweeted
New on our Engineering blog: Creating in-house source control.
In May, we merged around 2,500 code changes per day. In September, we merged more than 30,000 per day. As a result, we became bottlenecked by developer infrastructure built for human (rather than agent) scale.
Here, we share how we built a new version control system—and fully migrated our monorepo from git—in five months: anthropic.com/engineering/re…
