Thoughtworks Technology Podcast

Given the remarkable pace of change in software engineering throughout 2026, the latest edition of the Thoughtworks Technology Radar — vol. 35, due to be published November 4 — is an opportunity to take stock of the current state of the industry and to look ahead at how things might develop in 2027.

The themes in particular tell an interesting story about current challenges and areas of focus. They are: harness engineering at scale; putting more agents to work; beyond frontier models; and the economics of running AI at scale. Clearly, we're at a point where we're grappling with what it means to work with larger and more complex agent systems and the real material implications, whether that's in terms of money or how developers actually spend their time.

On this episode of the Technology Podcast, host Lilly Ryan is joined by Thoughtworks Chief Architect Chris Ford and Security Specialist Effy Elden (both of whom helped put volume 35 together) to discuss the themes in the new edition and unpack what they mean. They discuss everything from harnesses to local coding models and explore what Technology Radar Vol.35 might be able to teach us about software and what it means to be a developer today.

Explore Thoughtworks Technology Radar (vol.35 published Nov. 4, 2026): https://www.thoughtworks.com/radar

Learn more about Chris Ford's Agentic Engineering at Scale: https://www.thoughtworks.com/insights/books/agentic-engineering-scale

As fun as it is to discuss new terminology or debate the latest techniques, at some point the rubber needs to hit the proverbial road when it comes to AI. That's where things get really hard: when, say, your new agentic platform collides with the day-to-day realities of being an engineering team in a large organization with all the typical constraints and occasional firefighting.

On this episode of the Technology Podcast we're taking a closer look at one real-world experience of adopting an agentic platform by talking about some of the work Thoughtworks has been doing with Splio, an AI-first CRM platform. Talking with host Ken Mugrage, Thoughtworker Carolina Allende Amen is joined by Splio's VP of Engineering François Bonicel and CTO Philippe Donon to dive into the challenges, learnings and surprises that emerged as they worked together on Splio's ambitious agentic project.

Learn more about Thoughtworks' work with Splio: https://www.thoughtworks.com/clients/Splio

Dive deeper into the topic with this blog post written by Philippe and Thoughtworkers Amy Raygada and Johnny Sayers: https://www.thoughtworks.com/insights/articles/the-action-gap-customer-insight

Find out more about Thoughtworks' partnership with AWS and the Agentic Catalyst Program: https://www.thoughtworks.com/about-us/partnerships/cloud/aws/aws-software-isv

The way we think about and build with data is changing. Data lakehouses have become an industry standard, and conversation is turning to semantic and governance layers as organizations seek to optimize and leverage data for the AI era. However, the concept of 'data products' — treating data as something that needs to be deliberately managed and packaged in a way that's easily usable and consumable for the people that need it — remains crucial.

On this episode of the Technology Podcast, host Nate Schutta is joined by Thoughtworks colleague and Data and AI Lead Lorisa Perdoci and Lauren Hartman, Cloud Solution Architect at Microsoft, to discuss everything from data products to data agents. They also explore Microsoft Fabric, discussing how its evolution in 2026 to include new features and capabilities built for AI agents and today's data integration and governance challenges, reflects the direction of travel in this field.

The agentic era of software engineering began almost a year ago. And while much has changed in 2026, there's still a lot that hasn't been settled. One of the most important issues is how teams should collaborate. The idea of working with a spec may have considerable allure, but many questions remain: How should it be defined? Who owns it? How do we iterate with it? The fear of retreating back into waterfall is very real and requires vigilance.

On this episode of the Technology Podcast, hosts Ken Mugrage and Caer Sanders are joined by former Thoughtworkers Cassie Shum (formerly VP of Ecosystem and Product Engineering at RelationalAI) and Tim Cochran (recently a Principal at AWS) to discuss their new company Praxa Inc., a venture shaped by the industry's need to rethink the way we collaborate and structure our work in a world of AI agents. They discuss today's challenges, how software engineering is changing and how Praxa can help organizations navigate this period of evolution.

Learn more about Praxa: https://teaser.getpraxa.ai/

We've seen a huge amount of increase in interest around open-weight models in 2026. The reasons for this are multifaceted, ranging from the switch to per token billing, the evolving privacy landscape and improvements in open-weight model capabilities.

To unpack open-weight models and explore why and when we might want to use them, host Ken Mugrage is joined by Thoughtworkers Caer Sanders and Andre Almar. They discuss everything from the precise definition of the term and how they compare to other kinds of models, to governance and hardware challenges.

We've been thinking a lot recently about the status of code in a world where it's increasingly written and read by AI. Could the spec, for instance, become the primary way we interface with software systems? And if it does, will that mean humans no longer need to look at code at all?

At present, the idea of not looking at our code seems fanciful, possibly dangerous, but even within Thoughtworks there are conflicting perspectives about whether this might change. To some, code will always remain the primary artifact; to others, its role in how we build software is about to undergo a significant transformation.

On this episode of the Technology Podcast, Thoughtworks' Caer Sanders and Razin Memon join host Ken Mugrage for a debate about how the relationship between developers and code might — or might not — change in the final years of this decade. For Caer, despite the clear capabilities of AI, paying attention to code will always matter; for Razin, meanwhile, code's relevance is likely to decline as harnesses become more sophisticated and specification techniques evolve.

Whatever your view, listen for a frank and open discussion about an issue that will ultimately determine what the future of software engineering actually looks like.

Listen to our episode on harness engineering from May 2026: https://www.thoughtworks.com/insights/podcasts/technology-podcasts/what-harness-engineering

Read a recent blog post on thoughtworks.com arguing we still need to design code for humans: https://www.thoughtworks.com/insights/blog/programming-languages/should-still-design-code-humans

Harness engineering is still a new concept, but already we've noticed a challenge being consistently faced by technology leaders: how can a harness be used at scale across an organization to ensure consistency and controllability without undermining autonomy? To some extent it's a discussion that's reminiscent of platform engineering and, before that, DevOps, but, given the nature of AI agents, it's also unique to this particular moment.

On this episode of the Technology Podcast, host Ken Mugrage is joined by guests Thomas Squeo (Chief Technology Officer and Head of Advisory for the Americas) and Matt Kamelman (Innovation Choreographer) to explore why it's so important to scale harnesses effectively and the steps and processes that will allow you to do just that. Thomas and Matt recently wrote an article outlining how organizations should think about what they call 'enterprise harness engineering'; here, they unpack their ideas and explore what's required of engineering leaders and their teams.

Read Thomas' and Matt's article: https://www.thoughtworks.com/insights/articles/operating-system-enterprise-ai

Cloud was one of the main drivers of the early waves of AI adoption. However, as AI has become more and more embedded in systems and devices — in both consumer and enterprise contexts — it's becoming a bottleneck. This isn't just about costs (although yes, that issue is certainly surging up the agenda), it's also about how we optimize our architectures and improve device performance.

This is why conversation is turning to hybrid AI: embracing a hybrid approach that combines proprietary cloud services with local or on-device AI can help organizations deliver better experiences for users, whether they're consumers, other businesses or internal teams.

One company exploring this space is electronics giant Lenovo. In this episode of the Technology Podcast, host Prem Chandrasekaran is joined by Girish Hoogar, Lenovo's Global Head of Technology for Cloud and Software, to discuss why the company is embracing hybrid AI, how it's approaching implementation and what the implications are for other technologists.

As industry attention turns to local AI, listen for a first-hand perspective on what the trend actually means for engineering teams and their organizations.

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

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