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
Feature parity An Article martinfowler.com Whilst Feature Parity often sounds like a reasonable proposition, we have learnt the hard way that people greatly underestimate the effort required, and thus misjudge the choice between this and the other alternatives. For example even just defining the 'as is' scope can be a huge effort, especially for legacy systems that have become core to the business. Most legacy systems have 'bloated' over time, with many features unused by users (50% according to a 2014 Standish Group report) as new features have been added without the old ones being removed. Workarounds for past bugs and limitations have become 'must have' requirements for current business processes, with the way users work defined as much by the limitations of legacy as anything else. Rebuilding these features is not only waste it also represents a missed opportunity to build what is actually needed today. These systems were often defined 10 or 20 years ago within the constraints of previous generations of technology, it very rarely makes sense to replicate them 'as is'. softwarefeaturesrepair