Architecture Without Architects A Gallery by Bernard Rudofsky en.wikipedia.org Both a book and a MoMA exhibition of the same name by Bernard Rudofsky originally published in 1964. It provides a demonstration of the artistic, functional, and cultural richness of vernacular architecture. In 200 enlarged black-and-white-photographs, he showed various kinds of architectures, landscapes, and people living with or within architectures. Shown without texts or explanations, the visitors were just confronted with imagery that showed indigenous building traditions, which were very much at odds with the ideas of architectural modernism which had been promoted through NYC MoMA's Philip Johnson in his famous 1932 exhibition "Modern Architecture. International Exhibition". Non-architectsThe tacit wisdom of the body architecture
Agile as Trauma An Essay by Dorian Taylor doriantaylor.com The Agile Manifesto is an immune response on the part of programmers to bad management. Many a corner officeIntramural brownie pointsFeature factories agilemanagement
Many a corner office I want you to consider instead the possibility that Waterfall came to exist, and continues to exist, for the convenience of managers: people whose methods are inherited from military and civil engineering, and who, more than anything else, need you to promise them something specific, and then deliver exactly what you promised them, when you promised you’d deliver it. There exists many a corner office whose occupant, if forced to choose, will take an absence of surprises over a substantive outcome. surpriseplanning
Intramural brownie points Features don’t work, in the sense that they can be easily gamed. A brittle and perfunctory implementation, done quickly, is going to score more intramural brownie points over a robust and complete one. If the question is "does product A have feature X?" then the answer is yes either way. features
Feature factories We use the term feature factory as a pejorative to designate companies addicted to adding features, while accumulating incalculable so-called technical debt. This situation is driven by management for the convenience of marketing, and I am skeptical that a more faithful application of Agile principles will correct it. Indeed, I suspect Agile processes are constitutionally vulnerable to this kind of compromise. The presence of a feature can only indicate to a user if a goal is possible, behavior will determine how painful it will be to achieve it. ux