Local Code: 3,659 Proposals About Data, Design & The Nature of Cities A Book by Nicholas de Monchaux localco.de Local Code’s data-driven layout arranges drawings of 3,659 digitally tailored interventions for vacant public land in San Francisco, Los Angeles, New York City, and Venice, Italy. The natures of these found parcels is as particular as the cities that house them — land under billboards in Los Angeles, dead-end alleys in San Francisco, city-owned vacant lots in New York City, and abandoned islands in the Venetian lagoon — but have in common an unrecognized potential as a social and ecological resource. Names vs. The NothingLocal Code: The Constitution of a City at 42º N Latitude citiesurbanism
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