Matt and Georgia are joined by Georgie Healy, former Program Lead for Google’s AI Accelerator and creator of Attention Is All I Need, for a lively conversation about AI adoption, inclusion and the very human challenge of keeping up with rapidly evolving technology.

In this episode:

📰 The latest AI news The group unpacks:

• AI-related layoffs and whether AI is sometimes being used as a convenient excuse for restructuring
• The growing security risks created by autonomous agents
• New model releases and the impossible task of keeping up with them all
• The increasingly complicated relationship between data centres, housing, energy and public infrastructure

🧠 Are we still using our brains? AI can help us learn faster, explore new topics and stress-test our thinking - but it can also make it very easy to produce work we do not fully understand.

The group discusses:

• Why critical thinking and causal reasoning matter more than ever
• The risks facing graduates who rely on AI without understanding their own answers
• Why lived experience and systems thinking remain incredibly valuable
• How to use AI as a thought partner without creating yet more AI slop

🌍 Making AI feel more inclusive Why do some people embrace AI immediately, while others feel overwhelmed, excluded or actively resistant?

Georgie argues that AI literacy should be pro-people, not simply pro-technology. Rather than forcing people to use AI for work, adoption may be more effective when people can use it to create something useful, meaningful or genuinely fun.

✨ Using AI to bring ideas to life For the first time, people without traditional coding skills can build websites, create prototypes, explore hardware and turn ideas into something tangible - without necessarily needing a developer or CTO to get started.

👩‍💻 Who will shape the next era of technology? Georgie explains why women building cyberdecks, Tamagotchis, e-readers and other wonderfully niche hardware projects have changed her view of who will lead the next wave of AI-enabled innovation.

🔥 Plus, several hot takes:

• Georgia delivers an unexpectedly defence of M365 CoPilot
• Matt assigns everyone an unreasonable amount of homework
• Georgie explains why it is perfectly reasonable to feel complicated about AI
• The group concludes that technology can be useful, concerning and fun - all at the same time

A thoughtful, practical and occasionally chaotic conversation about creativity, critical thinking, representation and what it really takes to bring people along on the AI journey.

Guest: Lena Hall (Senior Director of Developer Experience at Akamai, formerly DevRel lead at Amazon Web Services and AI/Data Advocacy Director at Microsoft) joins Georgia and Matt to unpack the latest AI developments and what they mean for how we build software.

News Highlights

The episode kicks off with several major AI updates. The US government excluded Anthropic from a supplier list over concerns around WMD and surveillance policies - only for OpenAI to sign a government deal shortly after with similar language, raising questions about whether the decision was policy-driven or political.

Meanwhile, OpenAI released GPT-5.4, a reasoning-focused "thinking model" with tunable reasoning depth. Early feedback suggests stronger accuracy and less verbosity, though it consumes more tokens and is slightly more expensive to run.

The hosts also discuss a pledge from Meta, Microsoft, Google, and Amazon to fund new electricity generation to support AI infrastructure - a move framed as sustainability but widely seen as a practical response to AI's growing energy demand.

Finally, a new partnership between CVS Health and Google Cloud highlights a broader shift in hyperscaler strategy: AWS continuing to focus on horizontal infrastructure while Google invests more heavily in vertical AI solutions such as healthcare.

The Core Discussion: Engineering in the Age of AI

The main conversation explores how AI systems fundamentally challenge traditional software engineering practices.

Unlike deterministic systems, AI outputs exist on a spectrum of quality. A system may be operationally healthy yet still produce incorrect or harmful responses, creating a new category of production issues that are harder to detect and diagnose.

Lena argues that while organizations don't necessarily need entirely new AI platform teams, platform engineering must evolve. Teams need infrastructure for AI observability, evaluation frameworks, fallback mechanisms, and intervention controls. Without this foundation, individual product teams end up solving the same problems repeatedly.

A key takeaway is the need for clearer responsibility across three types of AI failure: capability issues owned by product teams, safety risks defined by leadership, and operational reliability managed by platform engineering.

The group also emphasizes the importance of product-level evaluation, focusing not just on model benchmarks but on whether AI actually works for real users. Effective evaluation frameworks measure capability, safety, and operational reliability, with scrutiny increasing for higher-risk applications.

For organizations adopting AI, Lena recommends a gradual approach: start with assistants for narrowly defined tasks, move to supervised agents, and only introduce autonomous systems once observability and governance are mature.

AI and the Human Factor

The discussion ends with the impact of AI on developers themselves. Engineers are spending less time writing code and more time making high-level decisions about architecture, system behavior, and trade-offs. While this can increase productivity, it also raises cognitive load and shifts responsibility toward more experienced engineers reviewing large volumes of AI-generated output.

Cool AI Pick

Lena's pick is Codex Spark, an ultra-fast model designed for executing well-defined tasks. Her preferred workflow combines reasoning models like GPT-5.4 for planning, then handing execution to Spark - highlighting a broader trend toward specialized models working together in AI development pipelines.

Cloud Dialogues – Episode 39 Guest: Ran Isenberg (Principal Software Architect at Palo Alto Networks, formerly CyberArk)

📰 News Roundup: AI Drama, Agent Governance & Layoff Myths

Episode 39 kicks off with a tour through the latest AI headlines – and there was no shortage of spice.

1. Anthropic publicly accused companies including DeepSeek, MiniMax, and Moonshot AI of using fake accounts to scrape and distill their models – a bold move that sparked debate given Anthropic's own history with training data practices. Google reported similar behaviour but stopped short of naming names. 2. We also explored OSO HQ, a new startup building visibility and governance tooling for AI agents operating across enterprise systems – essentially, "what are your bots actually doing?" 3. Meanwhile, rumours of an outage linked to Amazon Web Services' AI coding tool KIRO were clarified as human error rather than rogue AI. A useful reminder that not everything is Skynet. 4. The "Open Claw" / Claude Bot social experiment – later acquired by OpenAI – got a mention too. Interesting concept. Chaotic execution. Classic internet. 5. Finally, the hosts pushed back on the narrative that AI is directly causing tech layoffs. The real story? A correction cycle following years of over-hiring, empire building, and governance gaps – not a sudden robot takeover.

🧠 Main Discussion: AI Platforms – Welcome to the New Wild West

The core theme: AI tooling inside organisations is starting to look suspiciously like early cloud adoption. Shadow AI. Tool sprawl. Unmanaged access. Duplicate spend. No clear ownership.

Ran argued that platform engineering teams must step into the AI governance vacuum. That means: - Curating approved MCP servers and integrations - Defining and managing organisational "skills" (context files guiding AI agents) - Building observability into agent activity - Providing secure self-service templates for agentic services - Treating governance as an ongoing capability – not a slide deck exercise

The key message: publishing a framework isn't governance. Ownership, accountability, and maintenance are.

🔁 AI & The SDLC: Developers as Architects

The software development lifecycle is evolving fast. Developers are increasingly acting as architects and product owners – guiding AI agents through structured loops of:

Plan → Verify → Validate → Execute

Rather than writing every line of code, they're shaping specifications, validating outputs, and managing state through context files. Spec-driven development – where AI maintains project memory – emerged as a particularly promising model.

Ran's practical advice: - Test frameworks using real tasks (not demos) - Measure quality, cost, and performance - Gather feedback from actual developers - Roll out via pilot teams before scaling

Translation: treat AI adoption like an engineering transformation – not a hype cycle.

👀 Shadow AI: Blocking Isn't Strategy

The episode closed with a pragmatic take on "Shadow AI." Blanket bans on tools like ChatGPT don't build capability – they just push usage underground.

A smarter approach combines: - Education and cultural norms - Clear guardrails - Detection and observability tooling - Secure internal alternatives

Because people will use AI. The question is whether they'll use it safely – or secretly. Visit Ran's blog here: https://www.ranthebuilder.cloud/blog