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
Background textures of work An Article by Lucy Keer lucykeer.com One thing I've been enjoying about working as a technical writer is that the minute-by-minute texture of the work feels right. Something about formatting text, faffing about with SVGs, trying to rewrite a sentence more clearly... it's just enjoyable in itself, and I feel at home with it. ...Working as a programmer was very much not like that. There's something in the rough vicinity of professional dev work that I do like, which I could probably label as 'iterative hobbyist tinkering with websites'. I like working on something with a strong visual component, and I like to be inside of a fast feedback loop, and I'm mostly interested in just somehow bodging through until it works. I'm not very interested in either the computer-sciencey side of programming — data structures, algorithms — or the software-engineerey side of making things run reliably at scale in a maintainable way. So maybe it's not surprising that the minute-by-minute texture of professional programming was just... kind of bad. Occasional fun bits when I got into something, but the background experience was not fun. workproductivitymaking