The AI Native Dev - from Copilot today to AI Native Software Development tomorrow
Tessl
Último episodio
137 episodios
- Developers are about to write skills instead of code, and Microsoft's Daniel Meppiel argues the software factory that runs them needs versioning, a bill of materials and signed receipts before enterprises will trust it.
Watch all the AI DevCon NYC 2026 talks:
https://tessl.co/7jw
Recorded live at AI DevCon NYC 2026, Simon Maple sits down with Daniel, of Microsoft's Global Black Belt team and creator of APM (Agent Package Manager), to dig into why teams keep rebuilding the same skills, how to version a skill when the change is in its behavior rather than a method signature, and why skills can only ever be guidance while security controls stay deterministic. Then stay for Daniel's full DevCon talk, Version Your Factory, Not Just Your Code, on agent contracts, signed receipts and the evidence a regulated enterprise needs before it auto-merges.
What we cover:
– Why developers will write skills and prose instead of code
– Why teams keep rebuilding the same skills, and the case for a shared skill catalog
– Testing and versioning skills with evals: when is a change a major version?
– APM, lock files and an agent bill of materials for your software factory
– Skills are guidance, security controls are deterministic
– Daniel's AI DevCon talk: agent contracts, signed receipts and auto-merging on evidence
Chapters:
00:00:00 - Introduction
00:02:53 - Why developers will write skills, not code
00:05:49 - Why teams keep rebuilding the same skills
00:07:52 - Versioning the software factory, not just the code
00:09:48 - Testing and versioning skills with evals
00:14:09 - APM and the agent bill of materials
00:17:44 - Skills are guidance, controls are deterministic
00:21:02 - Skill catalogs, governance and measuring impact
00:24:46 - What developers do once the factory runs
00:28:08 - AI DevCon talk: Version Your Factory, Not Just Your Code
Book early for AI DevCon London 2027, 7–8 June at The Brewery, Moorgate:
https://tessl.co/wzi
🔔 Subscribe for weekly episodes on AI-native development
Would you let your software factory auto-merge on evidence alone? Tell us in the comments. - Paul Stack helped build Terraform. Now he says he'll never write another line of infrastructure as code, because an agent harness runs his team's production infrastructure instead.
Watch all the AI DevCon NYC 2026 talks:
https://tessl.co/kpo
Recorded live at AI DevCon NYC 2026, Guy Podjarny sits down with Paul, who spent years on Terraform at HashiCorp and on Pulumi before Swamp, to unpack why agents still trip over infrastructure state, what it takes to run a software factory that automates software delivery all the way to production, and why the people who know the system still make the calls. Then stay for Paul's full DevCon talk, From Page to Dossier, on a lights-out factory that does the 3am on-call legwork before anyone is woken up.
What we cover:
– Why agents still struggle with infrastructure as code, and why state is the hard part
– Model problem or harness problem: what an agent harness for operations needs
– Running an AI-first software factory from issue to production
– Blast radius, deterministic workflows and keeping credentials away from agents
– Why agents love toil, and why operators still own the judgment
– Paul's AI DevCon talk: turning a 3am page into a ready-made dossier
Chapters:
00:00:00 - Introduction
00:02:21 - From Terraform and Pulumi to Swamp
00:04:19 - How good are agents at infrastructure as code?
00:07:28 - Model problem or agent harness problem?
00:09:54 - Do we still need infrastructure as code?
00:12:53 - Inside an AI-first software factory
00:15:34 - Blast radius, determinism and agent credentials
00:18:48 - Agents love toil: the ops harness engineer
00:21:49 - Why software factories need ops
00:27:35 - AI DevCon talk: From Page to Dossier
Book early for AI DevCon London 2027, 7–8 June at The Brewery, Moorgate:
https://tessl.co/wzi
🔔 Subscribe for weekly episodes on AI-native development
Would you trust an agent harness to run your production infrastructure, or does your team still want a human on every apply? Tell us in the comments. - Automated software delivery is moving faster than the people who used to approve every release. LaunchDarkly co-founder and CEO Edith Harbaugh tells Guy Podjarny why rollback should be autonomous, why one-shot coding agents fail, and why the bottleneck has moved to the last mile.
What we cover:
– How automated software delivery and autonomous rollback take humans out of the 2 a.m. incident
– What makes a good feature flag, and when a homegrown system stops being enough
– Why coding agents need an explicit definition of success before they write a line
– Where release management fits in an AI software factory
– Feature flags for AI agents: switching models and prompts at runtime
– Running a company in the agentic coding era, and why teams should take dumb bets
Chapters:
00:00:00 - Introduction
00:02:16 - From quarterly releases to 30,000 changes a day
00:03:32 - Autonomous rollback and automated software delivery
00:06:25 - What makes a good feature flag
00:10:46 - Defining success for coding agents
00:16:42 - Agent fleets and engineers as reviewers
00:24:05 - Feature flags in the software factory
00:29:02 - The bottleneck moves to the last mile
00:39:24 - Runtime controls for AI agents
00:44:26 - Running a company in the agentic coding era
Build your software factory, one workflow at a time, with Tessl:
https://tessl.co/e0p
🔔 Subscribe for weekly episodes on AI-native development
Where has the bottleneck moved in your team's automated software delivery? Tell us in the comments. - Agentic coding has outgrown the text box. Maggie Appleton, staff research engineer at GitHub Next, argues that walls of CLI output and AGENTS.md files serve coding agents far better than the humans steering them. She walks through Chopin, the GitHub Next prototype where background agents turn a team's planning chat into a structured plan, and makes the case for agents that prompt you instead of waiting to be prompted.
What we cover:
– Why text-heavy agentic coding tools favor agents over humans
– Boundary objects: what AGENTS.md, skill files and MCP servers get right and wrong
– Multiplayer planning with coding agents in GitHub Next's Chopin
– Human-to-agent handoffs, formal verification and spec-driven development
– Why software quality is rising, not falling, with coding agents
– Which roles still matter: PMs, designers and engineers
Chapters:
00:00:00 - Introduction
00:02:14 - Inside GitHub Next and the Chopin project
00:05:57 - Why solo agents break team alignment
00:07:52 - Why coding agents struggle with design
00:12:16 - Boundary objects: AGENTS.md, skills and MCP
00:18:27 - Planning with coding agents as collaborators
00:26:49 - Multiplayer planning with background agents
00:31:57 - Agent handoffs and spec-driven development
00:37:41 - Quality, craft and who decides what to build
00:44:29 - Starting a career in agentic coding
Build your software factory, one workflow at a time, with Tessl:
https://tessl.co/j3d
🔔 Subscribe for weekly episodes on AI-native development
Should coding agents be prompting you more? Tell us in the comments how your team plans agentic coding work today. - AI attackers now move at machine speed, while most security teams still move at meeting speed. Former Robinhood CSO Caleb Sima has seen an AI attacker up close, and he argues the only way to keep up is to take humans out of the defense loop.
Caleb joins Guy Podjarny to unpack what changes when the attacker is an agent: one that hits every surface at once, reverses open-source code to find a 0-day, and once inside, burns your own AI tokens to keep going.
What we cover:
– Why AI attackers outran the red teamers' predictions, including 400 Linux 0-days found at 2.5 hours each
– Whether sandboxes can contain AI agents, and why external monitoring matters
– Who is accountable when your AI agent hacks someone else
– What actually changes when an AI attacker gets inside your company
– Deception, digital twins and forensic-grade detection
– Automating security: instant patching, one-way vs two-way doors, and security teams that ship the fix
Chapters:
00:00:00 - Introduction
00:02:58 - AI security goes mainstream
00:05:52 - Why AI attackers surprised the red teamers
00:12:50 - Can sandboxes contain AI agents?
00:18:03 - Security vs safety vs alignment
00:22:18 - Who's accountable when your AI agent hacks?
00:29:00 - What changes when an AI attacker hits you
00:36:47 - Detection, forensics and deception
00:44:10 - Machine speed vs meeting speed: automating defense
00:48:53 - Security teams that ship the fix
Build your software factory, one workflow at a time, with Tessl:
https://tessl.co/9ja
🔔 Subscribe for weekly episodes on AI-native development
Are your defenses ready for AI attackers, or still running at meeting speed? Tell us in the comments.
Más podcasts de Tecnología
Podcasts a la moda de Tecnología
Acerca de The AI Native Dev - from Copilot today to AI Native Software Development tomorrow
Welcome to The AI Native Developer, hosted by Guy Podjarny and Simon Maple. Join us as we explore and help shape the future of software development through the lens of AI. In this new paradigm of AI Native Software Development, we delve into how AI is transforming the way we build software, from tools and practices to the very structure of development teams.Our target audience includes developers and development leaders eager to stay ahead of the curve. If you're passionate about the future of software development and curious about how to leverage AI to build effective teams and groundbreaking software, this podcast is for you.Each week, we bring you insights into the latest AI tools and best practices, keeping you up-to-date with the cutting-edge advancements in the industry. Additionally, every two weeks, we present deep dives with experts and leaders in the AI and software development space, offering a glimpse into the future of AI development.Tune in to discover how AI will revolutionize your workflows, roles, and organizations. Get inspired by the latest tools and best practices, and prepare to be part of the next generation of software development.
Sitio web del podcastEscucha The AI Native Dev - from Copilot today to AI Native Software Development tomorrow, The Vergecast y muchos más podcasts de todo el mundo con la aplicación de radio.net

Descarga la app gratuita: radio.net
- Añadir radios y podcasts a favoritos
- Transmisión por Wi-Fi y Bluetooth
- Carplay & Android Auto compatible
- Muchas otras funciones de la app



































