Maeda's SIMPLICITY

Complex System = f(Simple Parts)

Yaron Goren from California in the US writes, "My favorite perspective regarding complexity is that something complex should be an integration of some very simple parts." I know that anyone who builds complex computational systems realizes that simplicity of parts not only has an intellectual aesthetic, but also is a requirement for retaining the implementor's sanity. Walking into a complex system of codes, with the seemingly infinite set of included files, libraries, and other non-intuitive happenings during compilation, can place your mind in a confused state of no-return. Neat and tidy structures and mechanisms are the lanterns in the invisible darkness of computational space.

Simple parts are most simple when there are few (versus many) parts. When there are fewer parts, there is an opportunity to distribute one's precious time in fewer directions which results in a higher quality per part. I learned this from legendary Ferrari designer Ken Okuyama of Pininfarina at a meeting of an advisory board for Philips on which we both serve. Ken talked about the Ferrari as a car that is designed with increasingly less parts as a way to place an increasingly exquisite amount of time into each of a Ferrari's individual components. Should I get a Ferrari or a Prius? I certainly still have time to reconsider ...