REVIEW: "97 Things Every Software Architect Should Know", Richard Monson-Haefel
Rob Slade, doting grandpa of Ryan and Trevor
"97 Things Every Software Architect Should Know", Richard
Monson-Haefel, 2009, 978-0-596-52269-8, U$34.99/C$34.99
%E Richard Monson-Haefel
%C 103 Morris Street, Suite A, Sebastopol, CA 95472
%D 2009
%G 978-0-596-52269-8 0-596-52269-X
%I O'Reilly & Associates, Inc.
%O U$34.99/C$34.99 800-998-9938 707-829-0515 nu...@ora.com
%O http://www.amazon.com/exec/obidos/ASIN/059652269X/robsladesinterne
http://www.amazon.co.uk/exec/obidos/ASIN/059652269X/robsladesinte-21
%O http://www.amazon.ca/exec/obidos/ASIN/059652269X/robsladesin03-20
%O Audience i- Tech 2 Writing 1 (see revfaq.htm for explanation)
%P 200 p.
%T "97 Things Every Software Architect Should Know"
Orient to the business, simplify, communicate, lead, meet
requirements, plan depth, specify, fit the situation, don't rush,
build foundations, fix problems early, re-use, lose the ego, guard the
scope, think ahead, have options, foresee implications, and pay (less)
now or pay (more) later--these are the pieces of advice given in 97
short items (they are too short to call them articles: maybe half a
dozen paragraphs each) contained in this work. Good reminders, but
nothing new.
Some pieces are less about software architecture, and more about the
details of coding and development, but these are relatively few.
Oddly, a number of suggestions emphasize data or content, which is not
a major factor in all systems. Possibly this reflects a Web or social
networking influence.
About half of the authors appear only once, some contribute half a
dozen pieces. Since there is no particular structure, and the authors
are all submitting individual advice, there are items which contradict
each other. The reader will have to make his or her own decisions
about simplification versus diversity, structure against autonomy,
programming rather than hands-off, scope vs change, solving problems
or not being a problem solver, and picking good tools and sticking
with then as opposed to not being married to a particular tool or
toolset.
Much of the advice in the book is good. Some is also questionable.
Some can be used immediately, some you will have to learn for
yourself.
copyright, Robert M. Slade 2010 BK97SASK.RVW 20101211
======================
rsl...@vcn.bc.ca sl...@victoria.tc.ca rsl...@computercrime.org
"Dictionary of Information Security," Syngress 1597491152
http://blogs.securiteam.com/index.php/archives/author/p1/
http://twitter.com/rslade
============= for back issues:
[Base URL] site http://victoria.tc.ca/techrev/
CISSP refs: [Base URL]mnbksccd.htm
Book reviews: [Base URL]mnbk.htm
Review mailing list: send mail to techbooks...@egroups.com
or techbooks...@topica.com