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

See All Reviews »

Review

Elizabeth White-Nadler
4.1
by Elizabeth White-Nadler - Oct. 1, 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 instruction for future software programmers. For those of us who know very little about software, it is remarkable that this writer is able to make the topic interesting and understandable.

See All Reviews »

Elizabeth's Rating

Overall
4.1

Good
from 13 answers
Quality
4.2
Facts
4.0
Fairness
4.0
Information
4.0
Sourcing
3.0
Style
4.0
Accuracy
4.0
Balance
3.0
Context
5.0
Popularity
3.5
Recommendation
3.0
Credibility
4.0
More How our ratings work »