Exploring the fundamentals of software engineering

You might think you know software engineering, but what are the really fundamental elements? What are the concepts, ideas and practices that are completely essential? What makes software engineering what it is? Thoughtworker Nate Schutta and Dan Vega are attempting to address those questions in their upcoming book with O'Reilly, The Fundamentals of Software Engineering. Covering topics ranging from reading code through to the importance of learning to learn, it promises to offer a fresh insight into the skills and knowledge needed to be a successful software engineer. In this episode of the Thoughtworks Technology Podcast, Nate and Dan join hosts Neal Ford and Ken Mugrage to discuss the book and to dive into what really are the fundamental elements of software engineering. Listen for a fresh perspective on the discipline and a deep dive that shows it's about far more than just writing code. Learn more about The Fundamentals of Software Engineering: https://www.oreilly.com/library/view/fundamentals-of-software/9781098143220/

Thoughtworks Technology Radar Vol.32 was published at the start of April 2025. Featuring 105 blips, it offered a timely snapshot of what's interesting and important in the industry. Through the process of putting it together, we also identify a collection of key themes that speak to the things that shaped our conversations. This time, there were four: supervised agents in coding assistants, evolving observability, the R in RAG and taming the data frontier. We think they point to some of the key challenges and issues that industry as a whole is currently grappling with. To dig deeper and explore what they tell us about software in 2025, regular host Neal Ford takes the guest seat alongside Birgitta Böckeler to talk to Lilly Ryan and Prem Chandrasekaran. They explain how the themes are identified and discuss their wider implications. Read the latest volume of the Thoughtworks Technology Radar: https://www.thoughtworks.com/radar            

The term 'vibe coding' — which first appeared in a post on X by Andrej Karpathy in early February 2025 — has set the software development world abuzz: everyone seems to have their own take on what it is, how it's done and whether it's a bold new chapter in the history of programming or an insult to anyone that's ever written a line of code. Clearly, then, we need to talk about vibe coding — and that's precisely what we do on this episode of the Technology Podcast. Featuring Thoughtworkers Birgitta Böckeler (AI for Software Delivery Lead) and Lilly Ryan (Cybersecurity Principal), who join hosts Neal Ford and Prem Chandrasekaran, we dive into the different understandings and applications of the concept, and discuss what happens when a meme collides with reality.

Nearly ten years after the first edition of Infrastructure as Code was published by O'Reilly, Kief Morris is publishing a third edition of the book. But why a new edition now? What's changed in technology and business over the last decade? Quite a lot, as it happens. To talk about what's new — both in the infrastructure world and in the book itself — Kief Morris joins host Ken Mugrage on the Technology Podcast. They discuss each edition and what's new in this one, and dive into the infrastructure challenges and issues that need to be tackled in 2025, from tooling and deployment to maintenance and infrastructure evolution. Learn more about Infrastructure as Code, Third Edition: https://www.thoughtworks.com/en-gb/insights/books/infrastructure-as-code-3rd-ed

AI is inherently dynamic: that's true in terms of the field itself, and at a much lower level too — models are trained on new data and algorithms adapt and change to new circumstances and information. That's part of its power and what makes it so exciting, but from a business and organizational perspective, that can make governance and measurement exceptionally difficult. How can we know that our AI is optimized for the right thing? How can we be sure it's oriented towards what we want it to be? This is where the concept of fitness functions can help. Broadly speaking, fitness functions are ways of measuring the extent to which a given solution is fulfilling its goals — so, in the context of AI, they can help teams ensure that AI systems are serving their intended purpose. In this episode of the Technology Podcast, Rebecca Parsons and Neal Ford — authors (alongside Pat Kua and Pramod Sadalage) of Building Evolutionary Architectures, the book which brought fitness functions into the software architecture space — join host Ken Mugrage to explore how the fitness function concept can help us better manage the dynamism of AI and, in doing so, overcome the challenge of bringing such systems into production. Learn more about Building Evolutionary Architectures: https://www.thoughtworks.com/insights/books/building-evolutionaryarchitectures-second-edition    

How can we better define and clarify architectures to ensure consistency and control? If, as Neal Ford and Mark Richards discussed on a recent episode of the Technology Podcast, software architecture intersects with many different facets of software development and delivery, what can we do to better manage architectures in a way that is adaptable and dynamic? Neal and Mark return to the guest seats to speak again to host Prem Chandrasekaran about fitness functions and architecture as code, and explain why rethinking our approach to software architecture can help ensure greater alignment with organizational needs and objectives.  

The release of DeepSeek's AI models at the end of January 2025 sent shockwaves around the world. The weeks that followed have been rife with hype and rumor, ranging from suggestions that DeepSeek has completely upended the tech industry to claims the efficiency gains ostensibly unlocked by DeepSeek are exagerrated. So, what's the reality? And what does it all really mean for the tech industry? In this episode of the Technology Podcast, two of Thoughtworks' AI leaders — Prasanna Pendse (Global Director of AI Strategy) and Shayan Mohanty (Head of AI Research) — join hosts Prem Chandrasekaran and Ken Mugrage to provide a much-needed clear and sober perspective on DeepSeek. They dig into some of the technical details and discuss how the DeepSeek team was able to optimize the limited hardware at their disposal, and think through what the implications might be for the industry in the months to come. Read Prasanna's take on DeepSeek on the Thoughtworks blog: https://www.thoughtworks.com/insights/blog/generative-ai/demystifying-deepseek

Generative AI's popularity has led to a renewed interest in quality assurance — perhaps unsurprising given the inherent unpredictability of the technology. This is why, over the last year, the field has seen a number of techniques and approaches emerge, including evals, benchmarking and guardrails. While these terms all refer to different things, grouped together they all aim to improve the reliability and accuracy of generative AI. To discuss these techniques and the renewed enthusiasm for testing across the industry, host Lilly Ryan is joined by Shayan Mohanty, Head of AI Research at Thoughtworks, and John Singleton, Program Manager for Thoughtworks' AI Lab. They discuss the differences between evals, benchmarking and testing and explore both what they mean for businesses venturing into generative AI and how they can be implemented effectively. Learn more about evals, benchmarks and testing in this blog post by Shayan and John (written with Parag Mahajani): https://www.thoughtworks.com/insights/blog/generative-ai/LLM-benchmarks,-evals,-and-tests

Software architecture necessarily intersects with a diverse range of critical things, including implementation, infrastructure, data and engineering practices. All these elements require serious consideration and reflection if you're to architect effectively.  To discuss these various intersections, Thoughtworks' Neal Ford and his long-time collaborator Mark Richards join host Prem Chandrasekaran on the Thoughtworks Technology Podcast. They dive into why these intersections matter, what they mean for software architects and how individuals and teams can go about addressing them. 

Who should be involved in the process of making decisions about software architecture? That's a question that's been puzzling Thoughtworker Andrew Harmel-Law for some time — so much so that he decided to write a book about it. The result is Facilitating Software Architecture. Published by O'Reilly in December 2024, it's both an argument for and a guide to involving more people in the architecture decision process. To discuss the topic and the book, Andrew joined hosts Neal Ford and Prem Chandrasekaran on the Technology Podcast. They explore why including more roles in software architecture matters today, some of the common objections to and risks of such an approach, alongside techniques and practices that can make doing it in fast-paced and dynamic organizations easier. "It's quite magical when you see this blossoming of understanding of what it is that architects do... It's not less architecture, it's more. It's just happening in a broader sphere." — Andrew Harmel-Law You can find Andrew's book on the O'Reilly website: https://www.oreilly.com/library/view/facilitating-software-architecture/9781098151850/