Zoning for diversity As production becomes increasingly clean and knowledge-based, as our urban economies tip dramatically to service industries, as racism and ethnic animosities ebb, and as the model of mixed use becomes more and more persuasive and visible, cities are in a position to dramatically rethink zoning as a medium for leveraging and usefully complicating difference, rather than simply isolating it. Michael Sorkin, 20 Minutes in Manhattan zoningrace
Bridges as walls The biographer of Robert Moses, Robert A. Caro, refers to the bridges and underpasses of the famed New York State parkways. These bridges and underpasses are quite low, intentionally specified by Moses to allow only private cars to pass. All those who traveled by bus because they were poor or black or both were barred from the use and enjoyment of the parkland and its "public amenities" by the technical design of the bridges. Even at the time of Robert Moses, a political statement of the form "We don't want them blacks in our parks" would have been unacceptable in New York State. But a technological expression of the same prejudice appeared to be all right. Of course, to the public the intent of the design became evident only after it was executed, and then the bridges were there. Ursula M. Franklin, The Real World of Technology politicsclassracediscriminationurbanism
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