http://en.wikipedia.org/wiki/Worse_is_better
In The Rise of Worse is Better, Gabriel claims "better" software is that which has the following characteristics:
Simplicity
the design must be simple, both in implementation and interface. It is more important for the implementation to be simpler than the interface. Simplicity is the most important consideration in a design.
Correctness
the design must be correct in all observable aspects. It is slightly better to be simple than correct.
Consistency
the design must not be overly inconsistent. Consistency can be sacrificed for simplicity in some cases, but it is better to drop those parts of the design that deal with less common circumstances than to introduce either implementational complexity or inconsistency.
Completeness
the design must cover as many important situations as is practical. All reasonably expected cases should be covered. Completeness can be sacrificed in favor of any other quality. In fact, completeness must be sacrificed whenever implementation simplicity is jeopardized. Consistency can be sacrificed to achieve completeness if simplicity is retained; especially worthless is consistency of interface.
Gabriel argues that early Unix and C, developed by Bell Labs, are examples of this design approach.
In The Rise of Worse is Better, Gabriel claims "better" software is that which has the following characteristics:
Simplicity
the design must be simple, both in implementation and interface. It is more important for the implementation to be simpler than the interface. Simplicity is the most important consideration in a design.
Correctness
the design must be correct in all observable aspects. It is slightly better to be simple than correct.
Consistency
the design must not be overly inconsistent. Consistency can be sacrificed for simplicity in some cases, but it is better to drop those parts of the design that deal with less common circumstances than to introduce either implementational complexity or inconsistency.
Completeness
the design must cover as many important situations as is practical. All reasonably expected cases should be covered. Completeness can be sacrificed in favor of any other quality. In fact, completeness must be sacrificed whenever implementation simplicity is jeopardized. Consistency can be sacrificed to achieve completeness if simplicity is retained; especially worthless is consistency of interface.
Gabriel argues that early Unix and C, developed by Bell Labs, are examples of this design approach.
Comments