4.7 • 53 Ratings
🗓️ 9 January 2025
⏱️ 44 minutes
🧾️ Download transcript
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.
Click on a timestamp to play from that location
0:00.0 | Welcome, everyone. My name is Prem Chandar Shaker, and I'm one of the regular co-hosts of the ThoughtWorks Technology podcast. Today we're joined by Neil Ford and Mark Richards, and they're going to be talking to us about the intersection of architecture |
0:22.1 | and a variety of aspects of the software development lifecycle. |
0:26.1 | We're going to do this in two parts. |
0:28.2 | In today's episode, we're going to talk about what these intersections are, and in an upcoming |
0:33.1 | episode, talk about how these correlate with code and implementation. With that, let's get |
0:39.7 | started. Hello, Neil and hello, Mark. Would you quickly introduce yourselves? Sure, I'll go first, |
0:46.1 | since you probably have heard my voice a lot. I'm sometimes a guest and sometimes host of this |
0:52.1 | podcast. I'm sitting in the luxurious guest chair today to talk |
0:56.6 | about this, since this is some IP I'm creating with my consistent teaching and writing partner, |
1:03.8 | Mark Richards, who's also joining us today. Hi, Mark. Hi, and thank you actually for having me on |
1:09.9 | yet another ThoughtWorks podcast. I think this is my third one, if I'm not mistaken, maybe even four. So it's great to be back on the podcast. |
1:20.0 | We're nothing if not consistent. |
1:23.5 | Excellent, excellent. It's great to have you both. And let's kick off today. So what is this |
1:30.4 | thing that we're calling the intersection between architecture and implementation? Sounds very intriguing. |
1:35.1 | We have a term that I did a little poking around and discovered, which I love, but is way too |
1:43.0 | obscure to talk about without providing |
1:45.3 | some context, which is the term nexus. So it's the term nexus, but it has a little hat over the |
1:52.3 | U and is pronounced nexus, and the definition is its plural nexus. So it's a combination of nexus, which is also legal, plural. But it's really |
2:05.7 | this idea that there's not one intersection of architecture and implementation. It's the intersection |
2:12.0 | between architecture and implementation and data and infrastructure and engineering practices, and in fact, nine |
2:21.5 | different places that we've concretely identified where architecture intersects with other parts |
2:27.1 | of the organization. |
... |
Transcript will be available on the free plan in -79 days. Upgrade to see the full transcript now.
Disclaimer: The podcast and artwork embedded on this page are from Thoughtworks, and are the property of its owner and not affiliated with or endorsed by Tapesearch.
Generated transcripts are the property of Thoughtworks and are distributed freely under the Fair Use doctrine. Transcripts generated by Tapesearch are not guaranteed to be accurate.
Copyright © Tapesearch 2025.