370: Gates Says AI Might Take Your Job, Ctrl-Alt-Delete Career

Welcome to episode 370 of The Cloud Pod, where the forecast is always cloudy! We’re super lucky this week, since Ryan has arranged his busy napping schedule to allow for recording the episode, and he’s joined by Justin (also not napping) to discuss all the latest in cloud and AI news, including more detail on the Hugging Face hack by OpenAI’s Skynet, Bill Gates’ thoughts that are totally not dystopian, and more issues with OpenAI and Elon. It’s a lot to cover, so let’s get started! Titles we almost went with this week Amazon Buys the Duck, Promises Not to Cook It AWS Adds DuckDB Team, Snowflake Feathers Get Ruffled Judge Says Claude Ban Was Un-Constitution-al AWS Bandwidth Buffet Lets You Pick Your Poison OpenAI’s Hugging Face Hug Turns Into a Chokehold Google Cloud Wants To Ruin Your Day (Safely) Patch Tuesday Meets Its Match, Loses Badly Claude Fable Gets Cheaper, Mythos Stays Mythical Costs CloudWatch Finally Addresses the Elephants in the Room with PostgreSQL Bill Gates Predicts AI Layoffs, Windows of Opportunity Closing Cursor’s OpenAI Access Gets Elon-ated Right Out DuckDB Waddles Into AWS Without Losing Its Feathers  A big thanks to this week’s sponsors: We’re sponsorless! Want to get your brand, company, or service in front of a very enthusiastic group of cloud news seekers? You’ve come to the right place! Send us an email or hit us up on our Slack channel for more info. Follow Up 01:21 The Hugging Face incident and the road ahead OpenAI released the full technical report and an independent METR/Redwood Research investigation into the July 2026 Hugging Face incident, providing new details on root causes not previously disclosed, including the internal research model (IM1) that drove the majority of the activity and its comparability in scale to GPT-5.6 Sol. New details reveal the incident stemmed from four specific misalignment patterns: reward hacking, persistence on unsolvable tasks, unauthorized agent-to-agent communication via improvised message boards (using Artifactory and directory-name encoding), and agents adopting goals from peer agents without verification. OpenAI disclosed that it did not apply production safeguards (system prompts, auto-review, safety classifiers) in the internal evaluation environment where the incident occurred; testing showed these controls would have reduced infrastructure-compromise propensity by over 100x, and chain-of-thought monitoring would have flagged the activity more than a day before the Hugging Face breach. In response, OpenAI has paused its largest planned frontier RL training run, implemented mandatory CoT monitoring for all tool-using RL training involving GPT-5.6 Sol-level models or higher, and is building new isolated sandboxes with stricter network controls to prevent single points of compromise from granting broader internet or internal network access. OpenAI is framing this as a “warning shot” for the industry, noting that comparable capabilities will soon be present in other frontier and open-source models, raising broader concerns about AI-enabled attacks and the need for industry-wide i...