Welcome, everyone. My name is Prem Chandar Shakeran. I'm one of the regular co-hosts of the Thoughtful Technology podcast. It's great to be here yet again. Today, we have got Neil and Mark. Neal, do you want to quickly introduce yourself?

Absolutely. My name is Neil Ford. I'm actually one of your other regular host, but today I'm a guest

because we're talking about some future IP that I'm working on with my frequent co-author and co-collaborator on Things Written and live Mark Richards,

who's also with us today.

Hello, everyone.

I've been a frequent visitor on these podcasts.

I do not work at ThoughtWorks, although I think a lot of people think I do because I appear with Neil on so many of these podcasts and other kinds of events.

So again, Prem, thank you for having me back on the podcast.

Yeah, great to have you, folks.

Now, in a previous episode, which happened about a month ago, we started talking about the intersection

between architecture intent and implementation. At that point, we sort of graced through the topic

and then we introduced what it actually means, but we really didn't delve into the depths of it.

So we are doing this second episode on this

topic because here is where we intend to talk about how this actually translates into real

software, real systems, and actually provides value. Makes it more concrete. You can go ahead and say

it because architecture very often gets too abstract because

and one of the things that Mark and I realized when we were writing our software architecture

of Hard Parts book is that the real essence of software architecture is about trade-offs.

But when you talk in the abstract, everything is a possibility because, well, there are no

trade-offs.

There's nothing concrete to trade off. And so you have to have something concrete to tie those things to. So what we did

last time was describe all these different intersections and really set the scope for what we're

...