Monday, September 27, 2004

Facts and Fallacies of Software Engineering

by Asim Jalis

There is a discussion on Slashdot about "Facts and Fallacies of Software Engineering" by Robert Glass. Here is a link. The book looks interesting. But even more interesting is the format. It might be easy and even fun to write a book as a kind of a list, where the points do not have to form one continuous line of thought. This single-line-of-thought format is painful both for the reader and I suspect the writer. Also most real-world knowledge is not organized in this way. It is rather made up of nodes linked through a web of connections and associations. So how could this approach be used to write other kinds of books? 1. 20 Observations about Calculus. Or Facts and Fallacies of Calculus. This could simply jump from topic to topic, showing the connections and then move on. 2. 20 Ways to Reduce Risk in Decision Making. Or 20 Laws of Risk Reduction. Again, all the ideas we discuss could be subsumed into this. There is no need for logical organization or for big architecture. Etc.