Software's Dirty Little Secret

In other disciplines, engineering in particular, there exist treatises on architecture. This is not the current case in software, which has evolved organically over only the past few decades. All software-intensive systems have an architecture, but most of the time it's accidental, not intentional. This has led to the condition of most software programming knowledge being tribal and existing more in the heads of its programmers than in some reference ... Full Story »

Posted by Kaizar Campwala
Tags Help
Subjects: Sci/Tech
Topics: Computers
Editorial Help

To:


Separate email addresses with commas.
25 recipients max.

Note:

Reviews

Show All | Notes | Comments | Quotes | Links
Silhouette_sml
4.5
by Randy Morrow - Jun. 22, 2008

Good article presenting a fairly compelling case for the establishment of accepted standards (as is pointed out, exist in other areas) in the writing of software.

See Full Review » (13 answers)
Silhouette_sml
4.3
by Naomi Isler - Jun. 18, 2008

It's hard to comment on something about which one knows nothing. But I wonder if this explains what appears to be the unnecessary complexity of some technological devices, the inability of many of these devices to communicate with each other even though they are of the same genre, the problems that arise when major conversions are undertaken, and the inability of simple humans to keep up. If it doesn't explain stuff like that, what does?

See Full Review » (9 answers)
Silhouette_sml
3.1
by Philippe Habib - Dec. 14, 2008

Grady Booch is one of the more respected names in computer science, as such I was dissapointed that he didn't have a deeper insight and a more complete discussion of the topic.

See Full Review » (11 answers)
Member_photo_thumb
4.1
by Elizabeth White-Nadler - Jun. 18, 2008

This is an interesting piece for even those readers who know very little about how the instruments we use, our computers, cellphones, ATM's, actually work. Based on an interview with expert "software archaeologist" Grady Brooch, Greenemeier explains the evolution of software and why there is not a codified method for developing it. He also explains why it is so important, in economic terms, to have a systematic approach. Finally, he describes how we can provide more uniform ... More »

See Full Review » (13 answers)
Fabportrait_smallsquare_180x180_thumb
3.5
by Fabrice Florin - Jun. 18, 2008
See Full Review » (2 answers)
Silhouette_sml
3.2
by Joe Pallas - Jun. 18, 2008

This is an important topic that received disappointingly shallow coverage, even for a "Q & A" presentation. Obviously, the interview format doesn't lend itself to multiple sources, but maybe a "round-table" style article would have allowed more perspectives in. There are plenty of strongly-opinioned people in this field, after all.

See Full Review » (5 answers)
Member_photo_thumb
4.0
by Kaizar Campwala - Jun. 18, 2008
See Full Review » (1 answer)
Silhouette_sml
4.1
by Bill White - Jun. 18, 2008

Grady Booch is a very well known guy in the world of commercial application development. He sort of gets it right. He states that there is no real architectural vision for most software projects. But what does he mean by architecture, anyway? I always thought architecture was a set of mental models for understanding the structure of something - a building, or a computer program, or a government project, or anything. The problem with this is that there is (1) no real continuity ... More »

See Full Review » (7 answers)

Comments on this story Help (BETA)

NT Rating | My Rating

Ratings

3.8

Good
from 8 reviews (50% confidence)
Quality
3.8
Facts
4.5
Fairness
4.3
Information
4.0
Insight
2.0
Sourcing
3.8
Style
4.0
Accuracy
3.0
Balance
4.0
Context
4.0
Enterprise
2.0
Expertise
2.0
Originality
2.0
Relevance
5.0
Popularity
3.9
Recommendation
3.4
Credibility
4.6
# Reviews
4.0
# Views
5.0
# Likes
1.0
# Emails
1.0
More
How our ratings work »

Topics

(See these related stories.)

Links Help

No links yet. Please review this story to add some!