Bölümler

  • Your Software Factory Needs a Bill of Materials | Daniel Meppiel
    19 Nov 2026

    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.

    Daha fazlasını göster Daha Az Göster
    1 sa. ve 1 dk.
  • Paul Stack: I'll Never Write Infrastructure as Code Again
    17 Nov 2026

    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.

    Daha fazlasını göster Daha Az Göster
    1 sa. ve 2 dk.
  • Edith Harbaugh: Code Is Cheap. The Last Mile Isn't.
    10 Nov 2026

    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.

    Daha fazlasını göster Daha Az Göster
    49 dk.
  • Maggie Appleton: Agentic Coding Has Outgrown the Text Box
    3 Nov 2026

    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.

    Daha fazlasını göster Daha Az Göster
    52 dk.
  • Caleb Sima: AI Attackers Move at Machine Speed
    27 Oct 2026

    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.

    Daha fazlasını göster Daha Az Göster
    55 dk.
  • Your Coding Agent Should Never Hold a Credential
    22 Oct 2026

    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.

    Daha fazlasını göster Daha Az Göster
    30 dk.
  • Snyk's Manoj Nair: Skills and MCP Are the New npm
    20 Oct 2026

    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.

    Daha fazlasını göster Daha Az Göster
    47 dk.
  • Maria Gorinova: Feedback Loops That Fix Your Codebase
    13 Oct 2026

    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.

    Daha fazlasını göster Daha Az Göster
    38 dk.