The source code for SimCity Local Code was Sorkin’s attempt to design a whole city from scratch—with one big twist. The whole thing had been written as if it were the byzantine, nearly impossible to follow codes and regulations for an entire, hypothetical metropolis. The effect is like stumbling upon the source code for SimCity. Sorkin’s exhaustively made point was that, if you know everything about a given metropolis, from its plumbing standards to its parking requirements, its sewer capacity to the borders of its school districts, then you could more or less accurately imagine the future form of that city from the ground up. Geoff Manaugh, A Burglar's Guide to the City Local Code: The Constitution of a City at 42º N Latitude rulesregulations
Politics and the English Language An Essay by George Orwell jarango.com Never use a metaphor, simile or other figure of speech which you are used to seeing in print. Never use a long word where a short one will do. If it is possible to cut a word out, always cut it out. Never use the passive where you can use the active. Never use a foreign phrase, a scientific word or a jargon word if you can think of an everyday English equivalent. Break any of these rules sooner than say anything outright barbarous. ruleswriting
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