Hi everyone, Quick update: I’m excited to share that I’ll be speaking at Red Hat Summit 2026 in Atlanta. My lightning talk is titled: “GPUs take flight: Safety-first multi-tenant Platform Engineering with NVIDIA and Red Hat OpenShift AI” I’ll be sharing practical lessons from building multi-tenant GPU platforms: isolation, quotas, guardrails, OpenShift AI patterns, and what it really takes to run AI/ML workloads safely at scale. 📍 Red Hat Summit 2026 🗓️ Tuesday, May 12, 2026 🕥 10:30 AM EDT 📌 Discovery Theater 1 I wrote a short post with more details here: https://lucaberton.com/blog/red-hat-summit-2026/ If you’re attending Red Hat Summit, DM me or simply reply to this email. It would be great to meet in person, exchange notes, and talk AI infrastructure, OpenShift, GPUs, and platform engineering. See you in Atlanta, Luca

At KubeCon EU 2026 in Amsterdam, I had the pleasure of sitting down with Kat Cosgrove — one of the most influential people in the Kubernetes ecosystem right now. Kat is Head of Developer Advocacy at Minimus, an elected member of the Kubernetes Steering Committee, technical lead for SIG Docs, and owner of the Kubernetes Release Team subproject. So yes — she is very busy. We talked about one of the biggest topics in the cloud native world right now: security.

From speaker to Master of Ceremonies 🎤 Cloud Native Rejekts EU 2026 in Amsterdam on 21st March was special. When the organizers asked me to MC the event at Miro HQ, I immediately said yes. Rejekts has always been one of my favorite parts of KubeCon week: raw technical content, zero marketing fluff, and a room full of people who genuinely build, run, break, and improve the cloud native ecosystem. Together with Julia Hahn, I had the pleasure of welcoming 300+ engineers for a full day of Kubernetes, open source tooling, security, platform engineering, runtime stories, user experiences, and the kind of talks that deserve way more visibility. That is what makes Cloud Native Rejekts so important. Many talks do not make it into KubeCon + CloudNativeCon simply because there are thousands of submissions and limited slots. Rejekts gives those ideas a second stage — and often, some of the best technical conversations of the whole week happen there. MC-ing taught me something new: - Being a speaker is about delivering one story well. - Being an MC is about connecting every story, keeping the room alive, respecting the schedule, supporting speakers, reading the audience, and creating space for the hallway track where the real magic happens. - A few lessons I will take with me: - Energy is contagious. - Brevity is respect. - Names matter. - Timing matters. - The hallway is part of the program. - Community is built in the spaces between talks. Huge thanks to the Cloud Native Rejekts organizers, all speakers, volunteers, sponsors, and everyone who showed up with curiosity and energy. If your KubeCon CFP gets rejected, do not stop there. Submit to Rejekts. And if you are attending KubeCon, block the day before for Cloud Native Rejekts. You will not regret it. https://lucaberton.com/blog/master-of-ceremonies-cloud-native-rejekts-2026/

At Sequoia, we see that speed is the best predictor of start-up success. Most companies are focused on AI as a productivity enhancer. Few are focused on the potential of AI to change how we work together. Block is showing what it looks like to fundamentally rethink organization design, ultimately harnessing AI to increase speed as a compounding competitive advantage. Two thousand years before the first corporate org chart, the Roman Army solved a problem that every large organization still faces: how do you coordinate thousands of people across vast distances with limited communication? Their answer was a nested hierarchy with a consistent span of control at every level. The smallest unit was the contubernium, eight soldiers who shared a tent, equipment, and a mule, led by a decanus. Ten contubernia formed a century of eighty men under a centurion. Six centuries made a cohort. Ten cohorts made a legion of roughly 5,000. At each layer, a named commander held defined authority, aggregated information from below, and relayed decisions from above. The structure (8 → 80 → 480 → 5,000) was an information routing protocol built around a simple human limitation: a leader can effectively manage somewhere between three and eight people. The Romans discovered this through centuries of warfare. Even today, the US Army's hierarchical chain follows a similar pattern. We now call it "span of control," and it remains the governing constraint of every large organization on earth. https://block.xyz/inside/from-hierarchy-to-intelligence

Cursor now lets companies run AI coding agents on their own infrastructure, keeping source code and build data in-house to meet security and compliance needs. https://thenewstack.io/cursor-self-hosted-coding-agents/