Difference between revisions of "User:Misfit138/The Arch Way v2.0"

From ArchWiki
Jump to: navigation, search
(Expedient)
Line 24: Line 24:
 
'''''easy, or quick; convenient'''''
 
'''''easy, or quick; convenient'''''
  
The simple, elegant and versatile system must offer expedience where practical, but  expedience can be sacrificed in favor of any of the above. It must be sacrificed whenever implementation simplicity is jeopardized
+
The simple, elegant and versatile system must offer expedience where practical, but  expedience can and will be sacrificed in favor of any of the above. It must be sacrificed whenever implementation simplicity is jeopardized. When expedience is compromised by a resulting complexity of user interface, it must present its complexity without unnecessary complication.

Revision as of 15:59, 7 October 2009


Simple

without unnecessary additions, modifications, or complications

Simplicity is the primary principle. All other principles must be sacrificed in favor of design simplicity. Implementation simplicity is more important than interface simplicity.

Elegant

Combining simplicity, power, effectiveness, a quality of neatness and an ingenious grace of design

The French aviator, adventurer, and author Antoine de Saint-Exupéry gave us perhaps the best definition of engineering elegance when he said “A designer knows he has achieved perfection not when there is nothing left to add, but when there is nothing left to take away.”

It is slightly more important to be simple than elegant.

Versatile

capable of doing many things competently; having varied uses or many functions

A simple and elegant system often becomes versatile by nature, but must be designed as simple first and foremost. Versatility must be sacrificed in favor of simplicity. Also less important than elegance, but more important than expedience.

Expedient

easy, or quick; convenient

The simple, elegant and versatile system must offer expedience where practical, but expedience can and will be sacrificed in favor of any of the above. It must be sacrificed whenever implementation simplicity is jeopardized. When expedience is compromised by a resulting complexity of user interface, it must present its complexity without unnecessary complication.