again thanks to everyone on the forum who is handling the effort to organize such a nice activity.
my question here regarding the book: why were these skills related to Software architect. generally speaking why do these make more sense for the software architects more than other people? do they apply to other profession? isn't these skills general management level skills that apply to everyone in such position?
I keep wondering what makes this different than any other "self development" book that is not specifically put in the context of "Software Architect".
The skills discussed in the book and the principles behind them are generally transferable to many different areas.
My focus was to slant the content of the book toward common issues, concerns and challenges that are faced by architects on a regular basis; and frame it from an architecture perspective.
One of the goals of the book was to help bring awareness to those in the technical ranks of specific development areas that may not be on their radar (but are flashing red lights to those in management that are watching and observing).