Thoughtworks
103 episodes listed below
PRESS PLAY
The Thoughtworks podcast plunges deep into the latest tech topics that have captured our imagination. Join our panel of senior technologists to explore the most important trends in tech today, get frontline insights into our work developing cutting-edge tech and hear more about how today's tech megatrends will impact you.
Based on 6 episodes we listened to · September 2026
It connects AI's promises to the engineering controls, team structures, and measures required to make those promises useful in practice.
Thoughtworks Technology Podcast treats AI as an engineering and organizational problem, examined through conversations among ThoughtWorks practitioners and outside guests.
The AI agent can write code; you still need someone willing to click merge.
Press play if you want
Short reviews from the PlayNext desk, based on the episodes we processed.
A sober follow-up on vibe coding that keeps circling maintenance, security, and what breaks later.
This episode looks back at vibe coding six months on, and the main point is that the term has stretched until it is doing too much work. The conversation keeps coming back to a plain question: who can keep this stuff running once the novelty fades?
A grounded look at human-centered AI strategy, from governance and consent to the tradeoffs of transparency.
Prem Chandrasekaran and Tiankai Feng keep the focus on human-centered AI strategy, returning to governance, creativity, consent, transparency, and the human factors that decide whether AI holds up in practice.
AI here is treated as an organizational design problem, not a product demo.
ThoughtWorks treats AI less like a shiny feature and more like a question of how organizations are built. The episode keeps returning to a practical tension: what deserves stewardship, what can be dropped, how shared meaning survives as systems change, and why Team Topologies…
A grounded look at AI adoption, measurement, and the CTO role as the conversation moves toward enterprise fluency.
ThoughtWorks uses its Looking Glass report to open a practical discussion about how AI is landing in client work, platform engineering, and the companys own agentic journey.
A calm look at AI as the next shift in software work, sharpened by an intern analogy.
The discussion treats AI as the next shift in software work, not as magic or a harmless extra. Nate Shuda, who calls himself a cloud solution architect, keeps the focus on day to day practice: prompting, guardrails, and the habits engineers build over time.
A grounded AI conversation about what changes when companies use it for real.
This episode treats AI as a working problem rather than a slogan: what are companies actually doing with it, and what changes inside the business when they do?
Agent platforms are judged here by permissions, guardrails, and production risk.
The episode focuses on what AI agent platforms are really for once they leave the demo stage and enter an actual organization. It keeps coming back to the hard edges: what data the system can reach, what code it can run, which permissions it inherits, and where a person still…
Long-form interviews on AI coding agents, infrastructure, and security, plus a recurring SED News roundup.
Founders and engineers on AI coding agents like Claude Code, and supply chain security.
Stack Overflow's Ryan Donovan interviews founders and engineers on AI agents, protocols, and dev tools.
Michael Kennedy interviews Python maintainers on packaging, security, web tools, and AI.
Michael Kennedy and Brian Okken run down the week's Python tooling, typing, and packaging news.
Matt Stratton interviews DevOps practitioners on security, platform engineering, and trusting AI-written code.
ThoughtWorks Technology Podcast uses Ken McGrage, Scott Davis, and Christopher Hastings to frame 'Mean time to shared understanding: Bridging the gap between citizen developers and developers' from the ThoughtWorks Berlin office.
With a high school band, the amplifier means "it just got louder. It didn't get any better, just louder."
If you had 10,000 pages in Confluence, would another 500 make your documentation problem better or worse? Worse.
At no part of this process did generative AI do any of the thinking for you; it eliminated busy work.
Technical writer Heidi Waterhouse tells Lily Ryan that documentation is 'the way we describe software to humans' and that most readers arrive 'pissed off' because the software has already failed them.
Unmesh Joshi describes astrophysicists at an institute in Pune who learned to run a data center because they had to manage their own data.
Brandon Cook describes an "autonomy slider" that sets how much freedom a coding agent gets by risk, scope and novelty.
Ricky Zachary's first episode as host of the Thoughtworks Technology Podcast covers AI/works, a platform built around guardrails, central observability and governance for AI-assisted software delivery.
Neil Ford and Mark Richards tell host Prem about the second edition of Fundamentals of Software Architecture, released in April after the first edition of February 2020.
Sarah Tarapawala, CTO of APAC at Thoughtworks, tells host Lily Ryan that digital business is moving from form-based websites to an "age of intent" where users describe what they want to AI systems like ChatGPT.
Software architect Nate Shuda argues that AI tools make software engineering fundamentals more important, not less, as they generate more code that engineers must read and manage.
The hosts return to vibe coding six months later.
Birgitta Bockeler and Ken McGrage talk with Matthew Skelton and Manuel Paiz about AI in engineering organizations and, more broadly, knowledge work.
Prem Chandrasekaran speaks with Tiankai Feng about making AI strategy feel more human.
July 2025 sets the question plainly.
AI is everywhere, but getting it into production is still where things get serious.
Looking Glass lands in practice.
Neil hosts co-authors Mark Richards and Raju Gandhi and O'Reilly editor Sarah Gray to discuss their early-release book 'Software Architecture Patterns, Anti-Patterns, and Pitfalls'.
Neil Ford and Brian Oliver walk through the four themes of Thoughtworks Technology Radar Vol.
Hosted by Alexei from Sao Paulo, Thoughtworks' Brandon Cook and John Coleman define durable computing as a program's ability to recover its state and "continue from where it left off." Brandon came to the topic through a client architecture assessment where teams had the happy path of their event-driven design right but lacked failure-path handling such as event replay.
Host Ken McGrage introduces guests Alessio Ferri and Jim Gumbly to discuss the themes of the latest ThoughtWorks Technology Radar, a curated list of technologies and techniques used internally.
A panel discusses the role of AI and MCP in IT operations and SRE, exploring why more than just APIs are needed.
A discussion with Andy Yates about Google I/O announcements, focusing on Gemini and Copilot, and their impact on users and organizations.
A discussion about a partnership between Mechanical Orchard and ThoughtWorks to modernize legacy systems using a platform and consulting services.
A panel discusses the upcoming book 'Fundamentals of Software Engineering' and the difference between software architecture and software engineering.
A panel of technologists discuss the differences between continuous delivery and continuous deployment, sharing insights from their experiences.
A panel discussion on AI-assisted refactoring, code quality, and the impact of tools like GitHub Copilot on legacy code.
Discussion on measuring and reducing the carbon footprint of cloud computing with experts from ThoughtWorks.
The hosts discuss Jugalbandi, a project using multiple AI systems to create digital public goods, accepted into the Digital Public Goods Alliance.
Panelists discuss the origins and evolution of ThoughtWorks' work in augmented and virtual reality, starting with a Lenovo enterprise VR headset project.