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
Building Momentum An Article by Dan Mall danmall.com Fight the Waterfall Start all of the pieces of work a little bit earlier. The key to starting work early is not succumbing to the pressure of having to finish the work. Don’t worry about finishing. If you’re a developer, you can start doing things while your design or information architect are working because a lot of your work actually isn’t dependent on their work. Some of it is, so you probably won’t be able to finish, but that shouldn’t stop you from starting. Share Work-in-Progress Early and Often When you share work-in-progress, share it with the caveat that no feedback is needed at this point. You’re simply sharing it to let people know where you are. For example, if you have to make 12 wireframes, share it when you finish 2 or 3. Rather than spending a whole week to drop 12 wireframes, share 2 – 3 wireframes every 2 days. The more often you do this, you start to build rhythm, and rhythm builds momentum. processworkcollaboration