If your solution to system failures is "tell developers to be more careful," you don't have an engineering strategy. You have a wish. And wishes don't scale. As humans, we are fundamentally fallible. We make mistakes. 🧵 (1/6)

The tech industry is currently obsessed with a dangerous illusion: the idea that software developers are just replaceable cogs in a machine. 🧵 1/8

Are companies really rehiring developers after AI layoffs? In my latest video, I dive into the data to show why writing code was never the hard part, and why AI tools are actually increasing the need for real software engineering. Watch now on @modernswe.bsky.social ➡️ youtu.be/VGE84CeeaMo

If you measure developer productivity by lines of code, you are completely missing the value of refactoring. A truly successful refactoring often results in fewer lines of code. 🧵 1/8

You can find your free course from our collection here ➡️ courses.cd.training/collections/... Make the most of this time to continue to learn, as that has always been the secret behind the very best software engineers! 4/4

As relevant as ever...

Most teams treat "coupling" as one vague, gloomy thing. It isn't. There are five distinct types, and each one has a different remedy. If you can't name your coupling, you can't fix it. Free guide ➡️ www.subscribepage.com/coupling

When Continuous Delivery is done right, it's the most effective approach to software delivery our industry knows. We're collaborating with Dr. Charlotte Fleming and Octopus Deploy to capture the state of Continuous Delivery for modern software teams.

📣 WELCOME (back) TO THE ENGINEERING ROOM Sam Newman 📣 Can AI replace software architects? No. 🗣️ LISTEN NOW: Apple - apple.co/43s2e0h Spotify - spoti.fi/3VqZVIV Amazon - amzn.to/43nkkRl Audible - bit.ly/TERaudible

Stop micromanaging AI code and start engineering outcomes. Explore the Acceptance Testing courses and master the future of programming today 🔗 courses.cd.training/pages/accept...

AI is incredibly fast at generating code, but its output is fundamentally non-deterministic. The hardest part of software engineering is exploring the problem, building a shared understanding, and clearly communicating what we actually want a system to do. 🧵 1/7

Software engineers are at the forefront of the disruptive change brought by agentic AI. While AI changes our work, it also refocuses us on our most important role. Tonight I’ll be discussing why ATDD is the strongest candidate for the next generation of programming language.

We have the answer to help optimise your team and development processes to do CD well and to reliably create high-quality, secure software. Manuel Pais (@teamtopologies.com) & I have a combined bundle of our courses FOR A BUY 1 GET 2 offer.

I had a fantastic time at AI DevCon yesterday - it was really nice meeting up with so many of you! Thanks again @tessl.io for the invite!

I'll be speaking at AI Dev Con by Tessl on June 1st. I'd love to see you there! I'll be delivering a talk on vibe coding and the future of programming. Tickets are available for live and virtual. If you're able, grab a ticket and join us there.

The rise of ai in software development actually makes REAL software engineering more critical than ever. While tools like GitHub Copilot, Claude Code, and Cursor make ai code generation cheap, they don’t solve the real bottlenecks. Video now on @modernswe.bsky.social ➡️ youtu.be/XDNXLdwq114

As co-author of the groundbreaking book @teamtopologies.com, Manuel has helped thousands of engineering leaders rethink how teams are organised for fast flow. His approach is practical, strategic, and grounded in real-world experience. 4/5

This is exactly why Manuel Pais's new course is perfect for engineering leaders and managers, heads of engineering and directors, technical leaders and architects, CTOs and organisational decision makers. 3/5

What is the fundamental measure of quality in software? It isn't speed, and it isn't security. Those things are important, but the absolute fundamental measure of quality in our industry is our ability to change the software. Everything else is secondary. 🧵 1/5

😎

I've started a new series on the @modernswe.bsky.social channel called 'AI Briefings'. Interviewing developers using AI in their projects in order for us all to share knowledge and experience in these unprecedented times! The first episode is available now ➡️

We have a new addition to our highly regarded "TDD & BDD: Design Through Testing" course that will revolutionise the way our students learn on our training site... 👇

Below are the 14 markers for successful Continuous Delivery within an organisation... Little bonus game... can you guess which one of these I think is the most important to get right? 👀 🧵 1/5

Are we writing fiction, or are we practising engineering? If you know my work, you know I generally prefer data and science over fiction. But Gene Kim’s fantastic novel, The Unicorn Project, made me realise something... 🧵 1/9

AI is helping us generate code faster than ever, but how do you ensure you aren't just deploying bugs at record speed? That is exactly why Continuous Delivery remains the state of the art for software development, providing the essential safety net your team needs. 🧵 1/6

Why do we so often treat refactoring as a "nice to have" rather than a core engineering discipline? We've all been in situations where we dread opening a specific file because the design is poor, obtuse, and overly complex. But the value of refactoring... 🧵 1/7

Does your development process attract innovators, or drive them away? We know that Continuous Delivery is the approach used by some of the most successful companies in the world. But why do they care so much about how their software is released? 1/8

Welcome to the Engineering Room Dan Abel! 📣 The nuances of engineering leadership and the evolution of high-performing teams. 🗣️ LISTEN NOW Apple - apple.co/43s2e0h Spotify - spoti.fi/3VqZVIV Amazon - amzn.to/43nkkRl Audible - bit.ly/TERaudible

Should software developers care about software architecture? If your answer is "no," we are back in the bad old days of the "Ivory Tower Architect" handing down rigid edicts to developers who are told exactly what to do. 1/9

Who is the "worst" programmer you have ever worked with? If you look back far enough, the honest answer is usually "Me." We often think "bad programming" is just about syntax errors or slow typing, but the real career-killers are habits that prevent us from learning.