AI-generated code: What has to be true for us to trust it without looking at it?

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

Tämä jakso on lisätty Podme-palveluun avoimen RSS-syötteen kautta eikä se ole Podmen omaa tuotantoa. Siksi jakso saattaa sisältää mainontaa.

Jaksot(100)

Rethinking the software development process for an era of specs and AI agents

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 ...

17 Syys 38min

Open-weight models: What are they and when should you use them?

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 ...

3 Syys 39min

Scaling the enterprise harness: How to achieve AI agent controllability across an organization

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 co...

6 Elo 45min

Embracing hybrid AI: How Lenovo is leveraging local, on-device 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 ...

23 Heinä 30min

What does the future of software engineering look like?

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 a...

9 Heinä 46min

What is 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 relationshi...

25 Kesä 40min

Database branching: Overcoming the bottlenecks of shared database environments

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 a...

11 Kesä 39min