The AI Native Dev - from Copilot today to AI Native Software Development tomorrow

Tessl

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.

  1. 1d ago ·  Video

    Paul Stack: I'll Never Write Infrastructure as Code Again

    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.

    Paul Stack: I'll Never Write Infrastructure as Code Again
  2. Nov 10 ·  Video

    Edith Harbaugh: Code Is Cheap. The Last Mile Isn't.

    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.

    Edith Harbaugh: Code Is Cheap. The Last Mile Isn't.
  3. Nov 3 ·  Video

    Maggie Appleton: Agentic Coding Has Outgrown the Text Box

    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.

    Maggie Appleton: Agentic Coding Has Outgrown the Text Box
  4. Oct 27 ·  Video

    Caleb Sima: AI Attackers Move at Machine Speed

    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.

    Caleb Sima: AI Attackers Move at Machine Speed
  5. Oct 22 ·  Bonus Video

    Your Coding Agent Should Never Hold a Credential

    Your coding agent should never hold a credential, and in a software factory that rule is only the start. Recorded live at the AI Security Summit in San Francisco, Simon Maple sits down with Eli Aleyner (Docker), Marcelo Sousa (Snyk) and Ian Livingstone (Keycard), co-authors of Agent Baseline, a security reference architecture for the AI software factory. The panel unpacks why agents have to be treated as fundamentally unpredictable actors, why sandboxing alone is not enough when skills and MCP servers make the supply chain dynamic, and why approval prompts collapse into fatigue. Marcelo's verdict: sometimes these are kids with chainsaws. What we cover: – The three levels of autonomy, from coding agents to fully agent-directed workflows – Sandboxing coding agents and injecting secrets at the egress point – Why the agent supply chain is dynamic: skills, MCP servers and cloned repos – Prompt injection, least privilege and agents monitoring other agents in the harness – Approval fatigue: YOLO mode vs CYA mode – Where to start securing your software factory on Monday morning Chapters: 00:00:00 - Introduction 00:03:14 - What Agent Baseline is and who it's for 00:04:17 - The three levels of software factory autonomy 00:06:53 - Sandbox boundaries and manufacturing trust in agents 00:09:22 - Why coding agents should never hold credentials 00:11:44 - The dynamic agent supply chain: skills and MCP servers 00:14:57 - Untrusted input, least privilege and agents watching agents 00:18:02 - Approval fatigue: YOLO mode vs CYA mode 00:20:22 - Are poisoned agent skills a supply chain problem? 00:22:45 - Where the panel disagreed, and where to start Monday Build your software factory, one workflow at a time, with Tessl: https://tessl.co/gsh 🔔 Subscribe for weekly episodes on AI-native development Which level of the software factory are you at today, and what are you locking down first? Tell us in the comments.

    Your Coding Agent Should Never Hold a Credential
  6. Oct 20 ·  Video

    Snyk's Manoj Nair: Skills and MCP Are the New npm

    Skills and MCP servers are the new npm, and AI coding agents are pulling them into enterprise codebases faster than security can keep up. Manoj Nair, Chief Innovation Officer at Snyk, joins Guy Podjarny at the Snyk AI Security Summit to map where enterprise agentic coding really stands. They get into why a 50,000-agent Claude Code rollout was pulled forward by weeks, why the autonomous attacker has some CISOs ready to accept an outage to patch faster, and how security is moving into the agent loop of the software factory. What we cover: – Why leadership and culture, not tooling, decide how fast enterprises adopt AI coding agents – The three risks of agentic coding: insecure output, the skills and MCP server supply chain, and agent behavior – Running coding agents locked down: sandboxes, agent identities and no open internet – Who owns the code an agent writes, and why AI-native organizations treat it as shared risk – Securing the software factory: security context in the agent loop and agentic remediation of the backlog – What still has to be solved before enterprises trust agents: identity, intent and behavior Chapters: 00:00:00 - Introduction 00:01:50 - The state of enterprise AI and agent adoption 00:09:45 - Leadership, culture and a 50,000-agent rollout 00:11:18 - Agentic coding risks: output, supply chain, behavior 00:14:29 - Locked-down coding agents and the security trade-off 00:18:01 - Who owns agent output? Compliance and accountability 00:22:54 - The autonomous attacker and security technical debt 00:27:56 - Securing the product vs securing the software factory 00:33:00 - Agentic remediation and the security backlog 00:40:18 - What enterprises need to trust AI coding agents Build your software factory, one workflow at a time, with Tessl: https://tessl.co/jw0 🔔 Subscribe for weekly episodes on AI-native development Where is your organization on the path from copilot to AI coding agents? Tell us in the comments.

    Snyk's Manoj Nair: Skills and MCP Are the New npm
  7. Oct 13 ·  Video

    Maria Gorinova: Feedback Loops That Fix Your Codebase

    Agent feedback loops are how a software factory maintains itself: agents mining their own session logs, PR comments and production signals, then fixing what they find. Maria Gorinova, member of technical staff at Tessl, explains how to build them, and why vague intent turns a loop into a mess. What we cover: – What a software factory is: repeatable workflows, a shared execution environment and agent feedback loops – Why agent context alone isn't enough, and where harness engineering comes in – The three stages of a feedback loop: analyze a data stream, find the problem, request the fix – Inner, middle and outer loops, from verifiers on every PR to self-healing in production – How Tessl's "comment diet" loop catches drift that no single PR causes – Operators and stewards: the human roles in a software factory Chapters: 00:00:00 - Introduction 00:02:36 - What is a software factory? 00:05:38 - From agents to context to harness engineering 00:09:15 - The three stages of an agent feedback loop 00:13:16 - Inner, middle and outer feedback loops 00:18:35 - Why vague intent breaks agent feedback loops 00:21:50 - Comment bloat, drift and the rule of three 00:25:48 - The software factory mindset 00:27:45 - Loops, feedback loops and meta feedback loops 00:32:45 - Operators, stewards and building your first loop Build your software factory, one workflow at a time, with Tessl: https://tessl.co/2uf 🔔 Subscribe for weekly episodes on AI-native development Which agent feedback loop would you build first in your own software factory? Tell us in the comments.

    Maria Gorinova: Feedback Loops That Fix Your Codebase
  8. Oct 6 ·  Video

    Legora CTO: Why AI Agents Need More Than a Chat Window

    AI coding agents now write almost all of Legora's code, with engineers running up to ten in parallel. Yet the CTO behind that shift thinks measuring adoption by tokens burned is a mistake. Jacob Lauritzen, CTO of Legora, joins Simon Maple to unpack what actually scales when agents do the typing, and where human judgment still has to stay in charge. What we cover: – How Legora's engineers orchestrate many AI coding agents at once, from shared local dev resources to cloud agent setups – An agentic loop that reproduces, fixes and tests bugs straight from Slack – Why token maxing is a bad way to drive AI adoption, and what to measure instead – Agent evaluation: regression testing the harness as models and prompts change every week – Decision models, the verifier's rule, and where autonomy ends and human judgment begins – Why AI agents need more than a chat interface Chapters: 00:00:00 - Introduction 00:01:47 - Legora's growth from $100M to $200M ARR 00:03:44 - Parallel coding agents and bug-fix loops 00:07:15 - Senior engineers vs AI-first engineers 00:10:10 - Why token maxing is the new lines of code 00:14:13 - What AI can and can't verify in legal work 00:17:30 - Decision models vs autoregressive LLMs 00:24:22 - Weekly model benchmarks and harness evals 00:26:58 - Why AI agents need more than a chat interface 00:35:03 - The verifier's rule and litigation strategy Build your software factory, one workflow at a time, with Tessl: https://tessl.co/lpg 🔔 Subscribe for weekly episodes on AI-native development Is token count telling you anything real about how your team uses AI coding agents? Tell us in the comments.

    Legora CTO: Why AI Agents Need More Than a Chat Window

About

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.

You Might Also Like