About the Book
Is the world perfect? No, it's not.
Is the perfect software possible? Yes, it is, if we define the perfect software as follows: one that meets user's expectations, does NOT have defects, is horizontally scalable, and "always works" without an additional dedicated production support team. The perfect software allows development pace acceleration on projects of any complexity, instead of typical slowdown. It doubles ROI per developer, team, and software.
If you prefer to deny or resist this statement, it's your choice, and no offense taken.
If you are curious to learn How Exactly you can achieve perfect software, then you are my reader.
I am a software development perfectionist, and anybody who has ever worked with me would confirm. I have successfully implemented software systems that meet my definition of "perfect". Everything that I write in this book is what I do on a daily basis. I believe that I should share my expertise with the world today so that better software systems can be built tomorrow.
Before you get too excited, I need to warn you that the road may not be easy. It will require dedication, passion, belief, study, study, and study. Did I mention to study? For that reason, techniques described in this book may not be practically doable for everybody out of the box. However, it will at least define what's realistically feasible, and what it takes to get there.
I think I am clear about what I want to achieve with this book. Let's see how it ends. My ambitions are endless, and my excitement does not let me sleep.
Thanks for reading it and supporting the right thing to happen!
Looking for Technical Editor
If you are a senior software engineer or above, and would like to participate in writing this book, please contact me at tengo_tutisani [at] hotmail [dot] com.
Ideal candidate will be fluent in English.
What I need: I will be sending you drafts of the book's chapters or the whole parts in word document format. I need to hear whether the material expresses the intent clearly. You will be expected to add your comments inline to the draft in any casual format, as long as I can understand what you mean. I will incorporate your feedback and will send you the improved drafts. We do this in iterations until the written material meets our combined expectations.
What you get: you will be mentioned as a technical editor in the book.
About the Author
Tengiz Tutisani is a software developer, architect, coach, trainer, and speaker. He focuses on making the world a better place, by building better software systems and coaching everybody else to do the same. His primary passion is saturated around Domain Driven Design, Software Architecture, and Extreme Programming.
You can learn more about Tengiz at his personal/professional website: www.tutisani.com