Sign up to save your podcasts
Or
Share The Rise of the AI Platform Engineer
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
The Rise of the AI Platform Engineer
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
View all episodes
By Georgia Smith and Matthew GillardCloud 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