
✍️ I just published "Best resources to learn about data and distributed systems" Happy learning 😊 #data #distributedsystem pierrezemb.fr/posts/distsys-…

🧑💻 Staff Engineer @clever_cloud 🤩 Distributed and Database Systems 🚀 Co-leader @finistdevs 💪 Squash player

✍️ I just published "Best resources to learn about data and distributed systems" Happy learning 😊 #data #distributedsystem pierrezemb.fr/posts/distsys-…

Researchers have used reinforcement learning to teach a 5-tonne John Deere skid-steer loader to perform complex acrobatic manoeuvres autonomously. Trained in simulation and transferred to a real machine, the system can balance on two wheels, navigate rough terrain, spin, and control its bucket before landing safely. The research demonstrates the potential of AI-driven automation for heavy construction and industrial machinery. Video Credit: @leggedrobotics / @ETH Paper: wevlv.co/4kltYys #engineering #technology

Le patch n’est pas optionnel
🚨We urge orgs to immediately patch the recently disclosed Oracle Java vuln CVE-2026-114938. This critical memory-corruption vulnerability, known as “Java4Shell,” affects the Base64 decoder of the x86-64 HotSpot JVM, part of the Java Development Kit. 🔗go.dhs.gov/5CC

Claude writes better code when it can verify its work. Checks that used to be expensive, like tests, benchmarks, and end-to-end runs, are now cheap. Here’s how the Claude Code team thinks about verification: claude.dev/blog/how-the-clau…

Exciting!


I published the slides, transcript, and made a recording from my HPTS'26 talk, "Please Implement A Quorum Database" transactional.blog/talk/plea…

Les tweets "j'ai essayé l'IA et ça m'a fait de la merde, c'est bien la preuve" me font penser aux tweets "on parle de réchauffement climatique, mais tu as vu la température aujourd'hui ? Rien à voir !". Pas plus lucide, pas plus honnête.

There’s no excuse for new software not to be logical, not to be deterministic. Investing in owning your testing, to be DST-first, and to accelerate the local development velocity of your team, is probably the best technical decision you can make.
We are actively rewriting software w/ TigerStyle & DST at Tempo. This is the role I am the most excited to hire right now. Please reach out. Need someone extremely AI pilled who also gets that "correct software" is the prerequisite to hillclimbing for performance.

I refuse some of the most important real-world systems in aviation cannot handle 200 QPS It’s almost an inconsequential amount of traffic for any modern system While I understand aviation is not considered “modern” by tech industry standards - come on…
FAA acting CTO Rebecca Guy: "When we started to see the occurrence where our network was having instability, we started to look at what was the cause. We saw two places that were actually pinging our network at a very high rate -- 1,000 connections over every 4 to 5 seconds." (That sure sounds like hacking!)


can’t believe i’ve never seen this before
After the FAA disaster we're all operating in a high-take environment, which is why I'm tapping the sign. how.complexsystems.fail/

Revolut shared the postmortem of their global cards outage of 5 hours. Some interesting (alarming?) notes: 1. They had no monitoring on database nodes going down (!!) 2. Across 3 regions, they ran 5 nodes, with #1. So a single node going down meant no zonal resillience (cont'd)
After 3 weeks of silence and me telling Revolut I’ll go ahead with my analysis publishing what was publicly observed (a single zone GCP outage took down global processing suggesting no zonal failover ability or process) Revolut finally responded & promised to share a postmortem.

We've used TLA+, Jepsen, and chaos testing in TiDB, and I still worry about what we failed to model. 😂 AI makes writing formal specs easier. But who verifies that we're specifying the right thing? Now we can formally prove the wrong thing 10x faster. Welcome to vibe verification. 😂
Formal verification is the Rust of software correctness. Most do not understand it, but just as people started shipping Rust because LLMs made it easier to write, we are now writing formal specifications because LLMs can generate them. The problem is, if you do not understand what you are writing, you can never be sure that it is "correct".

Oh boy, this sounds even more like a failure with a feedback mechanism. Time to find this feedback loop and break it. Most (but not all) loops need an overload on some physical or logical resource somewhere. @Microsoft I am on sabbatical to work on all kinds of metastable stuff😉
The servers we returned to service can become unresponsive again once they receive traffic; we're analyzing diagnostic data to determine what's triggering the behavior. In parallel, we're temporarily limiting which types of traffic can reach the affected infrastructure in some locations. Additionally, we're rebuilding a subset of affected servers using a previous configuration to validate if this prevents them from becoming unresponsive. More info under EX1550543 and MO1550821 in the Microsoft 365 admin center, as well as status.cloud.microsoft if the admin center is not available to you.

I strongly believe (hope?) humans should design and maintain software (likely in natural language). As this transition happens, we must also increase the level of abstraction used for verification (aka tests) Transcript Tests can help: andrew.nerdnetworks.org/blog…