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
Figma's Engineering Values: Craftsmanship An Article www.figma.com Craftsmanship is about thoughtfulness and care in the work we do. It means being deliberate about what we build and how possible it will be to maintain and extend in the future. A solution that will require revisiting in a month — because it’s not scaling, because it has a ton of bugs, because it doesn’t support all the use cases it needs to — is not useful to us and ultimately will generate pain for our users. What we trade off by living this value is (sometimes) day-to-day speed. It’s easy to imagine an engineering team that emphasizes moving fast over keeping things stable and bug-free -- like a team building a product that isn’t responsible for important user data and doesn’t support anyone’s livelihood. But given the role the Figma product plays in the lives of our users, we feel it’s worth it to ensure we hold a high quality bar for them. And in the long run, being thoughtful about how we build often reduces the complexity of ongoing development and new features regardless. craftsoftwarequality