"Thou shalt not have anti fragility, at the expense of the fragility of others" - Taleb, Antifragile
Why write a book at the same time as investigating the patterns that emerge from a whole new way of looking at software design and architecture?
Because that way of looking at software design and architecture is about dealing with the unknown; creating software that can adapt in the face of change.
If the book was written as a retrospective, navel-gazing and self-aggrandising pseudo confessional, placing the author on a platform as someone who was just smart enough to see the future, the whole thing would be fraudulent!
From the book:
"The book is intended to be a big step forward and it requires the reader to go on quite a journey! I could present those concepts in a "high-faluting", "wink-wink", "I know, trust me"*, "do it and I promise it will work" way with patterns, pictures, diagrams and stories alone. This is sadly the way of a lot of new-concept-introduction and architectural books in software today."
Instead I wanted to do something stronger, to be able to say:
"When I recommend something, it's for real and you can see it and I've risked my own projects and professional reputation on it."
In this book I'm going to do this for real with my own skin in the game before you even consider placing yours on the line.
I hope you enjoy the ride!