Hello, welcome listeners, and thank you for tuning into ThoughtWorks insights from Tech Leaders' podcast.

Today, Rebecca Parsons and myself, Neil Ford, are going to be discussing evolutionary architecture.

My name, as I said, is Neil Ford.

I am a director, a software architect, and meme wrangler at ThoughtWorks because ThoughtWorks lets you pick your own titles.

My website's Neal4.com and my Twitter handle is N-E-A-L-4D. It's the elite speak version of my name,

Neal Ford. Joining me today is the ThoughtWorks CTO, Rebecca Parsons. I'll let her introduce herself.

Thank you, Neil. It's good to be here.

And as Neil said, my name is Rebecca Parsons.

I'm the chief technology officer for ThoughtWorks.

I do have a website, Rebecca Parsons.com. And my Twitter handle is Rebecca Parsons.

I've been involved in various forms of agile architecture, really since I joined

ThoughtWorks back in December of 1999 when I was one of the few people who have as much gray hair

as I do that got to celebrate December 31st, 1999, because I wasn't mission critical on anything yet.

And that brings us around to the topic of this morning,

which is evolutionary architecture, which is something that Rebecca and I have both done a fair

amount of thinking about and talking about over the years. I had a developer works series for

almost two years around evolutionary architecture and emergent design?

And that's an important distinction, the evolutionary versus emergent.

When Neil and I first started talking about this, he was calling it emergent architecture, which I took some, I had some questions about because...

And the reason for that is, you obviously architecture is something that's that's

critical to a software system and in fact martin often defines architecture as either the things that

is is the most difficult to change or the things that an organization is most worried about that that that's what the key part of architecture is.

...