Googie architecture Where uses are in actual fact homogeneous, we often find that deliberate distinctions and differences are contrived among the buildings. But these contrived differences give rise to esthetic difficulties too. Because inherent differences—those that come from genuinely differing uses—are lacking among the buildings and their settings, the contrivances represent the desire merely to appear different. Some of the more blatant manifestations of this phenomenon were well described, back in 1952, by Douglas Haskell, editor of Architectural Forum, under the term “googie architecture.” Googie architecture could then be seen in its finest flowering among the essentially homogeneous and standardized enterprises of roadside commercial strips: hot-dog stands in the shape of hot dogs, ice-cream stands in the shape of ice-cream cones. These are obvious examples of virtual sameness trying, by dint of exhibitionism, to appear unique and different from their similar commercial neighbors. Mr. Haskell pointed out that the same impulses to look special (in spite of not being special) were at work also in more sophisticated construction: weird roofs, weird stairs, weird colors, weird signs, weird anything. Jane Jacobs, The Death and Life of Great American Cities Ducks and decorated sheds quirks
Reverse chronology bias Once you’ve had a taste of effortless updates, it’s awfully hard to back to manual everything. So they didn’t. And neither did thousands of their peers. It just simply wasn’t worth it. The inertia was too strong. The old web, the cool web, the weird web, the hand-organized web… died. And the damn reverse chronology bias — once called into creation, it hungers eternally — sought its next victim. Myspace. Facebook. Twitter. Instagram. Pinterest, of all things. Today these social publishing tools are beginning to buck reverse chronological sort; they’re introducing algorithm sort, to surface content not by time posted but by popularity, or expected interactions, based on individual and group history. There is even less control than ever before. There are no more quirky homepages. There are no more amateur research librarians. All thanks to a quirky bit of software produced to alleviate the pain of a tiny subset of a very small audience. That’s not cool at all. Amy Hoy, How the Blog Broke the Web Navigation by shibboleth timequirks
XXIIVV Webring A Website webring.xxiivv.com This webring is an attempt to inspire artists & developers to build their own website and share traffic among each other. wwwquirksblogging
Don’t Be an Ostrich An Essay by Chuánqí Sun medium.com You just handed off a major redesign. Three months of research, twenty-seven major revisions, and hundreds cups of coffee have all culminated in this pinnacle of glory. It’s finally done! Except it’s not. It’s not, even after you have answered every single question the developers have about your red-line. It’s not, even after you have addressed all the technical constraints developers encountered during the implementation. It’s not, even after you meticulously documented all the patterns and styles into a library for reference and reuse. It’s not, because neither you nor the developers have talked to a real user. At the bottom of your heart, you are secretly wishing: My design looks great on paper, so let’s keep it on paper. You are an ostrich. Post-occupancy evaluation
Post-occupancy evaluation Post-occupancy evaluation (POE) is a practice in the building industry where an architect would visit the building after its occupancy and interview its residents. It sounds like a great opportunity for collecting feedback and learning from mistakes, but it’s rarely practiced. Why? Many awe-inspiring, prize-winning architectures are half building, half sculpture. Often made of specially molded concrete and steel, they are extremely expensive to alter, let alone any alteration would also attack the architect’s prestige and pride. So whatever usability issues the POE identifies will remain as issues, unless the architect wants to accept the public criticism and shame that comes with the remodeling. In fear of criticism, an architect would turn down the opportunity for POE, and continue to design the same roof that would leak water in future projects. In fear of criticism, a developer would use customer service representatives as a shield against user complaints, while focusing on the “technical” aspect of things. In fear of criticism, a designer would close the contract as soon as the client accepts the design, even though none of the real users are represented by the client. architectureux