3 ms·
Speaking as an author of one of the articles in AOSA: What would you write if you were the author? Software architecture is very much just a bag of tips and tri
by rumcajz 12y ago
Speaking as an author of one of the articles in AOSA: What would you write if you were the author? Software architecture is very much just a bag of tips and tricks and rules of thumb. The result is, not surprisingly, pretty disparate.
- markbnj 12y ago>> Software architecture is very much just a bag of tips and tricks and rules of thumb. I think that agrees with the spirit of my original comment. To answer your specific question: I'm not sure. If a book about software architecture is going to look at two implementations - say, Audacity and Bash to take two examples from the first book - then it has to work very hard to find an architectural language that applies in common to both. If it does not, then all that has really been accomplished is to peel the onion on some interesting applications, and while that is valuable and makes for an enjoyable read, I don't feel like it gets us any closer to actually understanding what the "architecture" of a software implementation is. The word has to mean something more than "things we've done in the past."