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.
Raskin, in his essay on variety, suggested that the greatest flaw in city zoning is that it permits monotony. I think this is correct. Perhaps the next greatest flaw is that it ignores scale of use, where this is an important consideration, or confuses it with kind of use.
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.
We designers love artboards. From rough UI sketches to high fidelity mockups, we see ourselves as visual artists expressing ideas on artboards that have a pre-defined width and height. To start a new project, we declare the size of the artboard in the first step.
What about responsive design? Not a problem! We diligently design on three artboards — one for mobile, one for tablet, and one for desktop — with content elegantly adapting, scaling, reflowing, reordering, and reprioritizing. We proudly hand off the artboards to developers while patting ourselves on the back: this is how responsive design should be done.
After weeks of arduous engineering, the product finally comes out. We find, to our great dismay, that some copy is hanging off the grid, the focal point of the hero image has been cropped out, the font sizes don’t even come close to the type ramp. What went wrong? Can’t the developers just see everything on all those artboards?