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
The heart of systems engineering While the client has some knowledge of his symptoms, he may not understand the real causes of them, and it is foolish to try to cure the symptoms only. Thus while the systems engineers must listen to the client, they should also try to extract from the client a deeper understanding of the phenomena. Therefore, part of the job of a systems engineer is to define, in a deeper sense, what the problem is and to pass from the symptoms to the causes. Just as there is no definite system within which the solution is to be found, and the boundaries of the problem are elastic and tend to expand with each round of solution, so too there is often no final solution, yet each cycle of input and solution is worth the effort. A solution which does not prepare for the next round with some increased insight is hardly a solution at all. I suppose the heart of systems engineering is the acceptance that there is neither a definite fixed problem nor a final solution, rather evolution is the natural state of affairs. This is, of course, not what you learn in school, where you are given definite problems which have definite solutions. Richard Hamming, The Art of Doing Science and Engineering: Learning to Learn What the problem isComplete and consistent requirements