<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>02116nmm a22002537a 4500</leader>
  <controlfield tag="003">ES-BaAUN</controlfield>
  <controlfield tag="005">20230424152431.0</controlfield>
  <controlfield tag="008">221102b        |||    |o||j| 00| 0 eng d</controlfield>
  <datafield tag="022" ind1=" " ind2=" ">
    <subfield code="a">2575-5374</subfield>
  </datafield>
  <datafield tag="040" ind1=" " ind2=" ">
    <subfield code="a">ES-BaAUN</subfield>
    <subfield code="b">eng</subfield>
    <subfield code="c">ES-BaAUN</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Cardoso Llach, Daniel</subfield>
    <subfield code="e">author.</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="1">
    <subfield code="a">Between Accident and Control: Contrasting Traditions of Computational Design</subfield>
  </datafield>
  <datafield tag="260" ind1="3" ind2=" ">
    <subfield code="b">urbanNext,</subfield>
    <subfield code="c">October 16, 2020.</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">2426 words.</subfield>
  </datafield>
  <datafield tag="500" ind1=" " ind2=" ">
    <subfield code="a">Daniel Cardoso-Llach, Essay, expanding design practices, No Density, Technology and fabrication, WWW Drawing	</subfield>
  </datafield>
  <datafield tag="501" ind1=" " ind2=" ">
    <subfield code="a">Algorithms, Analysis, Architecture, Automation, Challenge, Comfort, Communication, Computation, Design process, Design thinking, Digital era, Drawing tool, Engineering, Essay, History, Mapping, New technologies, Research, Simulation, Smart tool, Technology, Transformation	</subfield>
  </datafield>
  <datafield tag="504" ind1=" " ind2=" ">
    <subfield code="a">This essay is an excerpt of WWW Drawing by Jaorg Abrams and Mehrdad Hadighi, published by Actar Publishers and Pennsylvania State University&#x2019;s Department of Architecture, Stuckeman School of Architecture and Landscape Architecture.
</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Since architects began to flirt with computers in the 1960s, debates about the role of computation in architecture have often been framed antagonistically &#x2013; as arenas for technophobes and technophiles to clash, each staking a claim on the unique value, or promise, of their respective practices. This dichotomy is tempting. On the one hand, images of automated design systems &#x2013; offering creative freedom, managerial efficiency, or &#x2018;personalized&#x2019; design solutions &#x2013; abound in architecture&#x2019;s six-decades romance with computation. Seductive and often reductive, these images outlined the contours of a computationally augmented practice of architecture, and captured the imagination of many architects in academia and industry, effectively ushering an entire academic sub-field.


</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">Architecture</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">Technology &amp; Fabrication</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">Data</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
    <subfield code="u">https://urbannext.net/between-accident-and-control/</subfield>
    <subfield code="z">Access to info</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="2">ddc</subfield>
    <subfield code="c">CF</subfield>
    <subfield code="n">0</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">2627</subfield>
    <subfield code="d">2627</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="2">ddc</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="a">9876543210</subfield>
    <subfield code="b">9876543210</subfield>
    <subfield code="d">2023-04-24</subfield>
    <subfield code="l">0</subfield>
    <subfield code="r">2023-04-24</subfield>
    <subfield code="w">2023-04-24</subfield>
    <subfield code="y">CF</subfield>
  </datafield>
</record>
