Style consists in distinction of form Writing about style in architecture, the nineteenth-century theorist Viollet-le-Duc asserted that "style consists in distinction of form," and complained that animals expressed this better than the human species. He felt that his contemporaries had "become strangers to those elemental and simple ideas of truth which lead architects to give style to their designs," and he found it "necessary to define the constituent elements of style, and, in doing so, to carefully avoid those equivocations, those high-sounding but senseless phrases, which have been repeated with all that profound respect which most people profess for that which they do not understand." Eugène Viollet-le-Duc, The Evolution of Useful Things Having quite lost sight of the principle style
The usages of life A Fragment by Eugène Viollet-le-Duc victorianweb.org During the sixteenth and seventeenth centuries architects not only paid attention to internal arrangements, but subordinated the designs for the exterior to them. The usages of life dictated the arrangement and the arrangement suggested the form of the building. This was the dominant principle in times of Classical Antiquity and the Middle Ages. The Timeless Way of BuildingForm follows function architecturefunction
Discourses on Architecture A Book by Eugène Viollet-le-Duc Style consists in distinction of formHaving quite lost sight of the principle
The heart of systems engineering While the client has some knowledge of his symptoms, he may not understand the real causes of them, and it is foolish to try to cure the symptoms only. Thus while the systems engineers must listen to the client, they should also try to extract from the client a deeper understanding of the phenomena. Therefore, part of the job of a systems engineer is to define, in a deeper sense, what the problem is and to pass from the symptoms to the causes. Just as there is no definite system within which the solution is to be found, and the boundaries of the problem are elastic and tend to expand with each round of solution, so too there is often no final solution, yet each cycle of input and solution is worth the effort. A solution which does not prepare for the next round with some increased insight is hardly a solution at all. I suppose the heart of systems engineering is the acceptance that there is neither a definite fixed problem nor a final solution, rather evolution is the natural state of affairs. This is, of course, not what you learn in school, where you are given definite problems which have definite solutions. Richard Hamming, The Art of Doing Science and Engineering: Learning to Learn What the problem isComplete and consistent requirements