January 31, 2005

Software Complexity

From Dan Murphy's Origins and Development of TOPS-20
This was one of the earliest occasions when I really began to appreciate the fact that a complex, complicated design for some facility in a software or hardware product is usually not an indication of great skill and maturity on the part of the designer. Rather, it is typically evidence of lack of maturity, lack of insight, lack of understanding of the costs of complexity, and failure to see the problem in its larger context.
Posted by ronlusk at January 31, 2005 11:12 PM