Ahmed Hendi

Yes, like 90% of you out there I'm building a software factory, more on that later … but now I want to tell you about a little side experiment I devised a couple of days ago. TLDR you don't need VMs or containers to develop and deploy full stack apps?

Unsafe AI Cyber Testing Isn’t a Breakthrough. It’s a Warning. The most revealing moment of the recent frontier lab episode wasn't that an AI model demonstrated offensive cyber capabilities. That was always coming. AI is democratizing intelligence, and adversaries get access to that capability at the exact same time defenders do. The real issue wasn't the model's capability. It was how it was tested, and what the episode reveals about the dangerous gap between frontier research and operational responsibility. From an operator’s perspective, this was not a security exercise. It was a capability demonstration executed with far too little regard for real-world consequences. Researchers may have viewed it as a harmless trial, but in cybersecurity, "harmless" depends entirely on containment. The moment you give a model arms and legs to run offensive operations, your first priority must be validating your own sandbox, not running a capture-the-flag exercise across live infrastructure. A disciplined approach starts from the inside out. Point the model at your own environment first. The initial flags to capture should be the flaws in your own sandbox: zero-day vulnerabilities, unexpected escape paths, or unauthorized internet connections. You shrink the blast radius before you widen the aperture. In that framing, what happened was elementary: they captured the wrong flag first. This operational oversight points to a broader risk I have been warning market analysts and enterprise leaders about for months. Autonomous cyber threats are not a distant theoretical exercise. They are arriving far faster than the market expects. As open-weight and closed-weight models proliferate, and as sophisticated actors gain the ability to fine-tune them, offensive automation will become standard tradecraft. A determined nation-state or well-funded syndicate with sufficient compute will push these systems to their absolute limits. When people look at generative AI today, they often point to its error rates and hallucinations as a reason to feel safe. In defense, an error rate is fatal. But on offense? It’s completely irrelevant. The model in this episode likely tried hundreds of hallucinated exploits, hit dead ends, and checked false positive paths before it found a way in. It didn't matter. Offensive AI doesn't need high precision, it relies on machine speed. This exposes the fundamental asymmetry of cybersecurity: adversaries only have to be right once; defenders have to be right 100% of the time. When an autonomous agent can probe millions of execution paths in seconds, that 1% defender gap becomes an ocean. That asymmetry dictates the playbook. You cannot fight autonomous, machine-speed attacks with human workflows, manual patching, or a stitched-together mosaic of legacy point tools. You can't go back to stitching point solutions—it’s a one-way street. There is only one viable path forward: you fight AI with AI. If offensive models can scan millions of endpoints instantly, defenders need equal visibility across their entire estate. That requires an enterprise security data lake, a unified platform that aggregates data across network, cloud, identity, and SOC endpoints. Precision AI, trained on proprietary enterprise context, must analyze that unified data in real time, surfacing zero-day exposure and neutralizing open paths before an attacker ever touches them. The takeaway from this incident is not that offensive AI capability is surprising. The lesson is that rapidly advancing models and unsafe testing practices are converging faster than legacy architectures can handle. Software promised us answers. Enterprises don't need answers anymore, we need outcomes. Every enterprise faces a clear fork in the road: adapt, rebuild your architecture around unified data, and fight AI with AI, or apply a band-aid and hope the world slows down.

Adding this effect in an App because everybody should. I have seen this being done by Instagram only. iOS 26 provides the native SwiftUI API: .tabBarMinimizeBehavior(.onScrollDown) Applied to the existing TabView, it: - Minimizes the tab bar when scrolling down. - Expands it when the user scrolls back up. - Uses the native Liquid Glass animation. - Works only on iPhone and requires iOS 26.

We evaluate frontier models across 4 domains (math, text-to-SQL, agentic search, and agentic coding), and find consistent degradation from single-turn to evolving multi-turn conversations. For simulation efficiency, we test on subsets of each benchmark and cap conversations at 7 turns (each of the 3 dynamics twice), though the framework naturally extends to longer horizons. *The 0% entries in SWE: some models loop on search tool calls when uncertain, and we count a turn as failed once its (per-turn) tool-call budget is exhausted. 🧵 4/N