The nomenclature of style: Brutalism, Minimalism, art history and visual style in architecture journals

The naming of styles or movements is a basic mechanism of the architectural journals. The announcement of new tendencies, groups or philosophies, gives a journal its character as ‘news’, and if such terms are taken up in general discourse this demonstrates the prescience of the editor and enhances the repute of the journal. The announcement of phenomenon such as ‘critical regionalism’ or ‘deconstructivism’ referred architectural developments to a context in socio-politics or philosophy, and thus aimed to provide at least an initial resistance to their understanding as the formal styles which they quickly became. A different strategy, or occasion, which this paper will discuss, is where the name of an architectural moment is given in the traditional form of an art historical style. Here the nomenclature of style and a certain attitude to form is introduced as the starting point for a more open ended critical inquiry. Two examples of this strategy will be given. The first is Peter Reyner Banham and the Architecture Review’s promotion of ‘Brutalism’ as an anti-aesthetic which took its conceptual form from early twentieth century art movements, particularly Futurism. The second, identified with Architectural Design in the 1990’s is ‘Minimalism’, a term describing a strand of the visual arts of the 1960’s which can be understood as an attempt to nuance and add seriousness to the present rampant nostalgia for the style of the architecture of the 1960’s.

Online help systems: Learning while working

Most widely-used computer software packages, such as word processors, spreadsheets and web browsers, incorporate comprehensive help systems, partly because the software is meant for those with little technical knowledge. This paper identifies four systematic philosophies or approaches to help system delivery, namely the documentation approach, based on written documents, either paper-based or online; the training approach, either offered before the user starts working on the software or on-the-job; intelligent help, that is online, context-sensitive help or that relying on software agents; and finally an approach based on minimalism, defined as providing help only when and where it is needed.