Ornament & Decoration
249. Ornament
Fine arts and decorative arts
Chapel of St. Ignatius, Seattle, 1995–7
- Bells
Presentable
I have sometimes wondered whether our unconscious motive for doing so much useless work is to show that if we cannot make things work properly we can at least make them presentable.
Sine qua non
What we see of a device is rarely the essential part, the sine qua non, but nearly always the superstructure which economy has imposed on it.
It seems that the work we call purely utilitarian is not more useful than its more ornamental counterpart. It is merely more economical.
Merely ornate
There is nothing merely ornate about nature: every branch, twig, or leaf counts.
Errors & Crimes
"A builder who hides any part of the building frame, abandons the only permissible and, at the same time, the most beautiful embellishment of architecture. The one that hides a loadbearing column makes an error. The one who builds a false column commits a crime."
— Auguste Perret
The problem with ornament
An ArticleContemporary architects are, however, increasingly engaging with ornamentation. The zenith was Grayson Perry and Charles Holland of FAT’s fairytale House for Essex (p64), but it does not serve as an indicator because the involvement of an artist has allowed an enhanced engagement with ornament until it surpasses mere decoration and becomes embodied in the architecture in a way that architects do not allow themselves to do. Think of FAT’s old work: the ornament is all contained within a surface - a facade - which allowed them to separate out the (Modernist) architecture from the (kitsch) superficiality of the elevation. Like Venturi before them, their ornament allowed them to have their ornamentally iced cake - and eat the Minimal Modernist sponge underneath.
Manifesto for Agile Software Development
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
Deliver early and continuously
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
Welcome changing requirements
Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
Self-organizing teams
The best architectures, requirements, and designs emerge from self-organizing teams.
Technical excellence and good design
Continuous attention to technical excellence and good design enhances agility.
Agility and sustainability
Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
The amount of work not done
Simplicity—the art of maximizing the amount of work not done—is essential.
The primary measure of progress
Working software is the primary measure of progress.
Build projects around motivated individuals
Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
Deliver working software frequently
Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
Business people and developers
Business people and developers must work together daily throughout the project.
Face-to-face conversations
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
Reflect, tune, adjust
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.