The 1916 Zoning Resolution Architecturally, what is striking about the 1916 legislation is that it sought to articulate a logical formula for achieving a public good in the absence of a specific vision of exactly what would actually be produced. Michael Sorkin, 20 Minutes in Manhattan regulationsconstraints
The air doesn't know about zoning boundaries Work uses suggest another bugaboo: reeking smokestacks and flying ash. Of course reeking smokestacks and flying ash are harmful, but it does not follow that intensive city manufacturing (most of which produces no such nasty by-products) or other work uses must be segregated from dwellings. Indeed, the notion that reek or fumes are to be combated by zoning and land-sorting classifications at all is ridiculous. The air doesn’t know about zoning boundaries. Regulations specifically aimed at the smoke or the reek itself are to the point. Jane Jacobs, The Death and Life of Great American Cities zoningregulationsseparation
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
Local Code: The Constitution of a City at 42º N Latitude A Book by Michael Sorkin www.goodreads.com The source code for SimCityLocal Code: 3,659 Proposals About Data, Design & The Nature of Cities regulationslawcities
“Design” is now “Product” An Article by Dorian Taylor dorian.substack.com Design has very little to do with what tools or methodologies you use, or what your job title is, or what you have a degree in, or even anything like “creativity”; design is about your relationship to constraints. Rather: to what extent are you defining constraints rather than just obeying them? Design is about taking a universe of possibilities and converging onto exactly one outcome. Being handed a set of constraints which you treat like immutable laws of physics (because many of them are) and solving within that envelope is what engineering is. To wit: what most designers are doing most of the time is actually a form of engineering, and engineers are always doing at least some design. This is because genuine design—the power to define constraints—is a privileged political position within an organization, and not everybody can occupy it. In other words, the “seat at the table” comes first. Design is Steve Jobs infamously dropping an iPod prototype into his fish tank, pointing at the bubbles coming out and yelling at his staff to make it thinner. It doesn’t matter what your title is; Jobs is the designer in that scenario. Steve Jobs designengineeringconstraints