Hello and welcome to the ThoughtWorks Beacon podcast.

I'm Neil Ford, and I'm here by myself today.

I'm a software architect and meme wrangler here at ThoughtWorks,

and one of the projects that I'm working on right now in that capacity is a book on evolutionary architecture,

which is a subject that I've been talking about for a while and been thinking about even longer.

And so has my colleague or CTO Rebecca Parsons.

She has also thought quite a lot about this subject.

And my colleague in the UK, Pat Kwa, as well.

So the three of us have gotten together and we're merging all of our ideas about what this idea of evolutionary architecture means.

And one of the things that we are in the process of developing is a definition of what we mean

by evolutionary architecture.

So we're still in the early days of this project, so this is very much a working definition.

So it very well may change

either minorly or significantly by the time we get finished with this work.

But for now, this is what we're working at.

And really, this idea of evolutionary architecture, we think, is important because the software

development world lives in the state of dynamic equilibrium

where everything is fine until some new factor comes in and has a wide-reaching influence

and it upsets the equilibrium and the system has to come to a new, a steady state.

We see this all the time in physics.

You see this in the phenomenon of molecular diffusion.

But the software development ecosystem works that way as well.

...