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

What if the whole point of your AI agent was to eventually make itself redundant? Dru Knox, Head of Product at Tessl, introduces the Tessl agent — a new interface built not just for AI-assisted coding, but for building the software factory that keeps improving without constant human input.

This is a conversation about loop engineering: how to set up automated feedback cycles so your agents get smarter, your code review gets tighter, and your team ships more without adding more toil.

What we cover:
– What the Tessl agent is and how it fits into the broader Tessl platform
– Loop engineering: why building automated feedback loops is the right place to start
– How the agent sets up and continuously improves agentic code review
– Why optimising your AI agent costs is usually the wrong lever to pull
– The case for open, modular software factories — and the risk of vendor lock-in
– UX expectations in the AI era: why outcome-oriented interfaces are now the baseline

🌐 Tessl: https://tessl.io
🔔 Subscribe for weekly episodes on AI-native development

What's your approach to building feedback loops into your agent workflows? Drop a comment — we'd love to hear how teams are thinking about this.
Join the AI Native Dev Community on Discord: https://tessl.co/4ghikjh

Ask us questions: podcast@tessl.io

Enterprises are finally being forced to care about their software development lifecycle — not because anyone suddenly got disciplined, but because agents cost money and the waste is now visible. When it was humans, it was "Timmy's just lazy." Now it's a line item. 
Simon Maple sat down with Patrick Debois (the godfather of DevOps, now DevRel at Tessl), Tammuz Dubnov (co-founder and CEO of Autonomy AI), and Daniel Jones (Head of Product at re:cinq) at AI Native DevCon London for a wide-ranging panel on AI enablement — who owns it, what's breaking, and what the organisations getting it right are actually doing differently. 
What we cover: 
– Who should own agentic coding adoption inside an enterprise, and why platform teams are already filling the vacuum 
– The "Timmy's lazy" problem: why agent cost visibility is forcing process discipline that humans never got 
– Why PR-based workflows are an anti-pattern inside enterprises once you're moving at agent speed 
– The PUMP framework (Plan, merge, polish): how one team is shipping features with developers, PMs, and designers all opening PRs –
 Rethinking what a "test" is in an agentic world — and why feedback loops matter more than first-pass correctness 
– The biggest mistake enterprises are making right now: piecemeal adoption with no mandate and no shared tooling 
 🌐 Tessl: https://tessl.io 
🔔 Subscribe for weekly episodes on AI-native development 

What's your team's approach to AI enablement — central mandate or letting individuals find their own way? Drop it in the comments.
Join the AI Native Dev Community on Discord: https://tessl.co/4ghikjh

Ask us questions: podcast@tessl.io

From the expo floor of AI Native DevCon London, Simon Maple went straight to the developers — speakers, attendees, and sponsors — to ask what's actually working with AI in 2026. The verdict? Outcomes beat outputs every time, 4,000-hour workloads are collapsing to 20 minutes, and the real bottleneck isn't code.

This is a conference floor walkthrough: honest, unscripted takes on harness engineering, evals, AI adoption mindsets, and the change management challenge that nobody talks about enough.

What we cover:
– Why measuring token usage, code commits, and outputs will lead your team astray
– How NearForm cut a 4,000-hour AML backlog to 20 minutes using agents
– Harness engineering and evals as the developer skills that matter most in 2026
– Why change management — not tooling — is the missing ingredient for real AI ROI
– How AutonomyAI is letting PMs and designers ship directly to production

Chapters:
00:00:00 - Welcome to AI Native DevCon London
00:01:03 - Chris Baty: Outcomes Over Outputs
00:05:15 - Martin: How Tooling Changed Everything
00:07:21 - Ryan: Harnesses, Evals and Skills
00:08:50 - Manny Saka: Plan Before You Prompt
00:11:58 - Cian O Maidin, NearForm: Real AI ROI
00:15:21 - Snyk: Building Trust at Scale
00:17:01 - AutonomyAI: Shipping Without Engineering
00:21:35 - Tessl Agent: Harness Engineering
00:22:41 - Closing Thoughts

🌐 Tessl: https://tessl.io
🔔 Subscribe for weekly episodes on AI-native development

Whether you're cautious or YOLOing it with AI — drop where you land in the comments.
Join the AI Native Dev Community on Discord: https://tessl.co/4ghikjh

Ask us questions: podcast@tessl.io

What does it mean to build securely when agents can negotiate their own guardrails? And what happens to the web — CLIs, frameworks, even the browser itself — when the primary user is no longer human? At AI Native DevCon London, Simon Maple sat down with two panels of experts to find out. 
First: a security roundtable with Joseph Katsioloudes from GitHub, Liran Tal from Snyk, and John Groetzinger from Cisco. 
Then: a web AI conversation with Dana Lawson from Netlify, Maximiliano Firtman from codemia, and James Moss from Tessl. 
What we cover: 
– Why 83% of enterprises plan to deploy AI but only 29% feel ready to do so securely 
– Prompt injection as a risk you have to accept — and how least privilege and sandboxing are your real defences 
– The "agent experience" concept: why systems built for human eyes fail at machine scale 
– Whether fundamentals like HTTP, semantic HTML, and accessibility still matter when agents do the heavy lifting 
– How WebMCP lets websites expose tools directly to agents 
— and why blocking them is like trying to turn off the sun
Join the AI Native Dev Community on Discord: https://tessl.co/4ghikjh

Ask us questions: podcast@tessl.io

Most engineering teams are still arguing about whether to use AI coding agents.

Ryan Lopopolo's team at OpenAI shipped an entire product with no human-written code — and onboarding a new engineer made the team faster within two weeks.

That outcome didn't come from better prompts. It came from what Ryan calls Harness Engineering: the systems, constraints, and feedback loops that sit around the agent — the context it sees, the tools it can call, the tests and linters that close the loop, and the asynchronous CI jobs that catch slop before it compounds.

We sat down with Ryan at AI Native DevCon London 2026, and he got into the specifics: how his team went from 3.5 PRs per engineer per week to 70, why he inverts spec-driven development (build the code first, distill the spec second), and what he means when he says it's "borderline negligent" not to use a billion tokens a day.

It's one of the most grounded, production-focused conversations we've had on The AI Native Dev. The trailer is live now — and the full episode drops this week.

#HarnessEngineering #AINativeDev #SoftwareEngineering
Join the AI Native Dev Community on Discord: https://tessl.co/4ghikjh

Ask us questions: podcast@tessl.io