Abstract and often ambiguous diagrams will never make up for real code. Never.
There are far too many "architects" who sit there all day drawing out massive diagrams of software systems, adding complexity that isn't needed, and in the end still not providing something that's usable.
You could fire those architects, hire some good developers, and actually get a software product developed, tested and in the field, well before those architects have "perfected" their "designs".
by Anonymous Coward writes:
on Wednesday June 23, 2010 @01:34PM (#32667494)
When did the on-topic (but incorrectly marked off-topic) parent poster say that diagrams shouldn't be used for such things? That comment specifically addresses software diagramming, which can indeed be done with SketchUp.
Diagramming works well for physical objects, where there is a 1-to-1 correspondence between reality and the drawing. It doesn't work well for abstract things like computer programs, where there is no such mapping.
When did the on-topic (but incorrectly marked off-topic) parent poster say that diagrams shouldn't be used for such things? That comment specifically addresses software diagramming, which can indeed be done with SketchUp.
Maybe it's marked offtopic because the book isn't about software architecture??
You see but you do not observe.
Sir Arthur Conan Doyle, in "The Memoirs of Sherlock Holmes"
Diagrams will never make up for real code. (Score:-1, Offtopic)
Abstract and often ambiguous diagrams will never make up for real code. Never.
There are far too many "architects" who sit there all day drawing out massive diagrams of software systems, adding complexity that isn't needed, and in the end still not providing something that's usable.
You could fire those architects, hire some good developers, and actually get a software product developed, tested and in the field, well before those architects have "perfected" their "designs".
Software architecture isn't like des
Re: (Score:5, Insightful)
Where does it say it can't be used? (Score:-1, Redundant)
When did the on-topic (but incorrectly marked off-topic) parent poster say that diagrams shouldn't be used for such things? That comment specifically addresses software diagramming, which can indeed be done with SketchUp.
Diagramming works well for physical objects, where there is a 1-to-1 correspondence between reality and the drawing. It doesn't work well for abstract things like computer programs, where there is no such mapping.
Re: (Score:0)
Maybe it's marked offtopic because the book isn't about software architecture??