What is code? It might sound obvious, but if you scratch the surface it becomes more difficult to articulate precisely what we mean. AI is complicating the picture further and changing the relationship developers have with code: when large amounts of executable code can be generated from high-level descriptions, what does it even mean to write code?

On this episode of the Technology Podcast, host Alexey Boas is joined by Thoughworks Distinguished Engineer Unmesh Joshi to discuss what code actually is and what it means to write, test, review and maintain code today. Building on Unmesh's recent article 'What is Code?' for martinfowler.com, this discussion dives into one of the fundamental building blocks of software while also thinking through the implications for 2026's engineering challenges.

Read Unmesh's article on martinfowler.com: https://martinfowler.com/articles/what-is-code.html

At the end of June, Thoughtworks and Martin Fowler convened an unconference-style event in Switzerland with a range of industry leaders. The aim was to reflect on the current challenges and learning around AI assisted and agentic software engineering and discuss the implications for the future — and, most importantly, what actions need to be taken today.

To review the event and dive into some of the topics that surfaced, host Ken Mugrage is joined by Thoughtworks colleagues Kief Morris (author of Infrastructure as Code) and Andrew Harmel-Law (author of Facilitating Software Architecture). They highlight some of the key ideas and issues that emerged from the event's conversations, ranging from developer identity to harness engineering.

Learn more about the European edition of the Future of Software Engineering Retreat: https://www.thoughtworks.com/about-us/events/the-future-of-software-development-europe-2026

Read Andrew's recent blog post that asks whether non-functional requirements could be a vital guardrail for AI-generated code: https://www.thoughtworks.com/insights/blog/architecture/non-functional-requirements-missing-guardrail-ai-generated-code

Database branching has, for a long time, been a troublesome piece in the modern developer workflow puzzle: a good idea in principle but in practice a slow and often expensive challenge. Get it right and you can accelerate productivity and remove bottlenecks; get it wrong and you're potentially creating all sorts of trouble for yourself, from privacy risks to additional complexity.

However, things are changing. Thanks to the emergence of new platforms such as Neon, Supabase and Databricks Lakebase, branching a database can become as familiar to developers as managing code branches and multiple environments with, say, Git and Terraform.

On this episode of the Technology Podcast, host Ken Mugrage is joined by his Thoughtworks colleague Cam Casher and Databricks' Kevin Hartman to discuss the work Thoughtworks and Databricks have been doing together on Lakebase. They discuss the platform, their experience using it with Spotify's Backstage and the opportunities database branching can offer software engineering teams in an increasingly AI-assisted and agentic world.

Read Cam and Kevin's recent series on using Databricks Lakebase with Backstage: https://www.thoughtworks.com/insights/blog/data-engineering/backstage-lakebase-databricks

Semantic diffusion, combined with the pace of technology change, makes talking about AI-adjacent practices and techniques incredibly diffficult. There are few better examples of this issue than the term 'spec-driven development'. Although it's not new — its coinage precedes our current AI moment — it has become ubiquitous over the last six months or so as software professionals attempt to develop a vocabulary for talking about how they're developing methods for working successfully with coding agents.

On this episode of the Technology Podcast, Birgitta Böckeler is joined by Laura Tacho — Developer Experience at AWS — to discuss all things spec-driven development. From competing definitions to different interpretations, implementations and workflows, the discussion provides a frank and grounded look at one of the most discussed and debated terms in modern software engineering.

Learn more about Laura's work by visiting her website: https://lauratacho.com/

Read Birgitta's article on spec-driven development on Martin Fowler's website: https://martinfowler.com/articles/exploring-gen-ai/sdd-3-tools.html

Learn more about The Future of Software Development Retreat discussed on this episode and explore some of the key insights: https://www.thoughtworks.com/about-us/events/the-future-of-software-development

'Harness engineering' is one of the most significant terms to emerge in software engineering in 2026. Broadly referring to the work done to control unpredictable AI agents and coding assistants, its use signals growing attention on what needs to be done to make agents reliable and consistent enough for production software in the real-world.

On this episode of the Technology Podcast, Birgitta Böckeler joins hosts Prem Chandrasekaran and Nate Schutta to explore what harness engineering actually is, how it should be done and why it should matter to software engineers working today. Having written a number of articles on harness engineering for martinfowler.com based on her experiences with AI-assistance, Birgitta is well-placed to explain the core concepts and implications.

Taking in everything from the practices and ideas that pre-date and inform harness engineering to integrating harness engineering into existing workflows, listen for a conversation that will provide much needed clarity on what's an essential topic in the industry.

Read Birgitta's article on harness engineering on martinfowler.com: https://martinfowler.com/articles/harness-engineering.html

Watch Birgitta's video on harness engineering beyond skills on YouTube: https://www.youtube.com/watch?v=uLWOLmeHOSE

Anthropic Mythos garnered significant attention when it was launched in mid-April 2026. Yet despite it apparently presenting an unprecedented threat to global software, you don't have to look to closely to see that this was an effective product launch as much as a story about the grave security risks of today's AI models.

But this isn't to say there aren't important implications for software developers, security professionals and other technologists. In this episode of the Technology Podcast, one of our new hosts Nate Schutta is joined by Chris Kramer to discuss Anthropic Mythos and Project Glasswing, unpacking what's hype and what really matters.

A few links for this episode:

Some more information about Project Glasswing: https://www.anthropic.com/glasswing

A story about how a small Discord group briefly had access to Mythos: https://daringfireball.net/linked/2026/04/23/discord-group-has-claude-mythos-access

How Mozilla used Mythos to discover Firefox bugs: https://www.wired.com/story/mozilla-used-anthropics-mythos-to-find-271-bugs-in-firefox/

In April 2026 we published a new edition of the Thoughtworks Technology Radar — volume 34. Like many recent volumes, this one was dominated by AI. However, while editions over the last couple of years have illustrated the dizzying proliferation of AI-related technologies, vol.34 indicates a degree of evolution in the field, demonstrated by a focus on consistency, reliability and mitigating the collaborative and individual challenges of working with AI. This is reflected in the four themes identified for this Radar: the challenge of evaluating technology in an agentic world; retaining principles, relinquishing patterns; securing permission-hungry agents; putting coding agents on a leash.

On this special Technology Radar episode of the Technology Podcast, host Ken Mugrage is joined by Alessio Ferri and Jim Gumbley to discuss the key themes in Technology Radar Vol.34. Diving into topics ranging from cognitive debt, harness engineering and the lethal trifecta, listen to gain a deeper understanding not just of the latest Radar but, more importantly, what AI-assisted and agentic software engineering really look like today.

Read the latest Thoughtworks Technology Radar: https://www.thoughtworks.com/radar

There's been a lot of discussion and debate in recent months about exactly how software engineering will be reshaped by AI. While it remains to be seen what the discipline will look like once things quieten down (if they ever do), one thing has been somewhat neglected: what does software engineering actually feel like in this AI-intensive environment? If we're no longer writing code, or even interfacing with it in the way we're used to, what does that mean for our professional experience?

On this episode of the Technology Podcast, host Ken Mugrage is joined by Nate Schutta to discuss the software engineering experience today and to dig deep into what the work feels like when AI agents change our relationship with code. Nate is one of the authors of Fundamentals of Software Engineering (alongside Dan Vega) and appeared on the podcast in May 2025 to discuss the book; with so much change having taken place since then, Nate is perfectly placed to offer a perspective on what software engineering means today for an industry navigating significant change.

Learn more about The Fundamentals of Software Engineering: https://www.thoughtworks.com/insights/books/fundamentals-software-engineering-book

Listen to Nate discuss the book on an earlier episode of the Technology Podcast: https://www.thoughtworks.com/insights/podcasts/technology-podcasts/exploring-fundamentals-software-engineering