3 Responses
Stay in touch with the conversation, subscribe to the RSS feed for comments on this post.
exploring the intersection of digital media, ambient informatics, and architecture
Stay in touch with the conversation, subscribe to the RSS feed for comments on this post.
Reading for Mon/Wed: Urban Computing and its Discontents (download and print the PDF)
Conclusions:
– conclusions that merely restate/summarize the main points of the essay are BORING.
– concluding gesture/gesture towards a conclusion
– instead of narrowing down (V), open things up (^)
– ex. what larger issues has your paper brought up that we should be thinking about?
– what are some questions that your paper might lead us to ask?
– use your conclusion to make people THINK. Think of it as an expansive, provocative paragraph rather than a narrow, rote one.
– DON’T WRITE BORING PAPERS!
Sentient Cities Exhibit Reactions
– importance of getting to know architectural firms — ex.. The Living (professionalization, networking)
– Too Smart City
- legal questions
- build questions (spring not stron enough)
- Proposal not meant to be carried out
– art projects
- difference between an art project and an architectural proposal
- art experiment with things / architecture solve problems
- protypes/ideas to get us to start thinking
- ex. one reaction to “Too Smart City” = this will never work. legal issues. why should garbage can spit up plastic but not glass?
== ex. not grandma can’t use the bench — but how can this exhibit make us rethink relationship between our lives and park furniture
– point of project to be funny provoke — chose to be arbitrary with it to make you think about decisions we/city makes
– technology and how it might be annoying — playing with idea that technology makes things easier
-0
- Should think about relationship between technology and architecture
– all projects in same room –
– doesn’t have to be same thing — use ideas in different places/different objects
– ex. student sleeping at desk – throw out of desk — if you’re sleeping — bangs on desk
** take kernel of idea and apply it in different contexts/different projects **