A single conversation with a wise man is better than ten years of study.
~ Chinese Proverb ~

Patterns for Organic Architecture - let it grow!

Jarosław Pałka

Bottom-up or top-down, emerging design, TOGAF, UML, BPMN, SOA, large scale, small scale, new shiny written by hipsters or good old legacy written by Iron Maiden fans?

How to build architecture of your system? How to transition your current design and don't get mad, don't waste time for

unproductive meetings, discussion, arguments and cheap talks, writing down business cases, searching for business value and justifying business justification.

After years of small and large projects, waterfall, Agile, Kanban, couple of paradigm shifts, couple of trend explosions, new and shiny tools and techniques. After all this I understood that whatever we want to believe it or not, we don't deliver code, business value or company success.

The only thing we do is we increase entropy of this world, by adding more and more complexity, that no matter how fast CPU executes our code, how much time and effort we put in quality, at the end of day each software will be destroyed by its complexity. Maybe ""Software is eating the world"", but for sure complexity swallows the software at the same time.

During this talk I would like to share with you a few patterns I have discovered, learned and stole over the years, a couple of obvious, well known tips&tricks, which we tend to forget about, so I gave them a name to make it easier to remember about them. I called them Patterns of Organic Architecture.

Why? Because the only thing that seems to be able to cope with complexity is nature. Nature doesn't plan, doesn't use advanced frameworks, doesn't have deadlines, meeting, memos and such. And still we discover more and more beautiful works of nature which amaze us with its simplicity.

This talk will prove that if you learn how nature works, how much you can learn exploring pyramids and that some of the systems have strange attractors, you will not need software enterprise principal architect on your team, because he will never ever again leave his ivory tower.

You will learn how to grow your system!

More talks