This shows you the differences between two versions of the page.
| lgru_notes [2012-02-25 14:12] – created 83.101.5.51 | lgru_notes [2012-02-25 14:17] (current) – 83.101.5.51 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ==== complexity, metaphors and tools ==== | ||
| - | # -*- mode: org; coding: utf-8; -*- | + | preludes & summaries |
| + | |||
| + | | ||
| + | * complexity often more easily understood in reverse | ||
| + | * importance of metaphor, problems with binary ' | ||
| + | * using ' | ||
| + | * technology is Promethian | ||
| + | |||
| + | summary | ||
| + | * computers are performance machines built out of metaphor | ||
| + | * metaphors direct our creative practice, (eg. git tree, file system, copy/paste, pipes) | ||
| + | * document or application centric views may be problematic. suggestions; more metaphors, assemblages, | ||
| + | | ||
| + | * complexity emerges out of interaction and assumptions | ||
| + | * importance of looking backward as well as forward | ||
| + | * from mute systems -> conversational systems | ||
| + | * find ways to make context more apparent. material, ephemera and objects. | ||
| + | |||
| + | 3 stage exercise | ||
| + | - image selection. "what tool is this?" and "how can this tool work with other tools?" | ||
| + | - groups ~5. explain each tool in circle, explain how they can work together, single shared metaphor | ||
| + | | ||
| + | |||
| + | introduction | ||
| + | |||
| + | questions? | ||
| - | * notes from chat w. femke | ||
| misc. | misc. | ||
| - | | + | * embodied tools |
| - | - tools as mechanisms for thought > process | + | |
| - | - tools as collaborator rather than instrument | + | |
| - | - reflexive use of tools | + | |
| - | - requirement / necesity for ' | + | |
| - | + | ||
| - | - position statement -> sketching in afternoon | + | |
| context | context | ||
| - | | + | * design as problems of collision (rather than problem solving or ' |
| - | - collision of source materials -> versioning & conflict resolution | + | |
| - | - collisoin " | + | |
| - | - heterogeneous systems -> unix pipes metaphor | + | |
| - | - role of metaphor adoption from print -> computing, computing -> computing, etc | + | |
| - | - ' | + | |
| - | - repreasenation | + | * representation |
| - | - ideology vs. pragmatism -> FLOSS positioning/ | + | |
| questions / problems | questions / problems | ||
| - | + | * context -> how to make more apparent/ | |
| - | | + | |
| - | - metaphors in use - print/ | + | |
| - | - what new mataphors? ' | + | |
| - | - tangible systems -> (qfwfq/ | + | |
| - | - connecting incompatible or partially compatible parts -> friction | + | |
| - | - toola as collaborators -> conversational interaction models | + | |
| - | - how to ' | + | |
| - | - document formats -> programmes -> VB Macro virus in Word -> ' | + | |
| frictions | frictions | ||
| - | | + | * e.g. pipes -> API -> ORB |
| - | - historic examples / other paths -> e.g. symbolics concordia, metafont, etc | + | |
| refs and misdirdections | refs and misdirdections | ||
| - | + | * http:// | |
| - | | + | |
| - | - http:// | + | |
| - | - http:// | + | |
| - | - http:// | + | |
| - | - http:// | + | |
| - | - http:// | + | |
| - | - http:// | + | |
| - | - http:// | + | |
| - | - http:// | + | |
| - | + | | |
| - | | + | |
| - | - http:// | + | |
| - | - dream machines ("a minority report" | + | |
| - | - agrippa -> book | + | |
| - | + | ||
| - | + | ||
| - | * preludes & summaries | + | |
| - | + | ||
| - | - a discussion of preludes and summaries | + | |
| - | - complexity best understood in reverse | + | |
| - | - importance of metaphor, problems with binary ' | + | |
| - | + | ||
| - | - technology is Promethian -> Epimetheus, brother of prometheus (hindsight, afterthought, | + | |
| - | + | ||
| - | + | ||
| - | - summary | + | |
| - | - computers are performance machines built out of metaphor | + | |
| - | - metaphors direct our creative practice, (eg. git tree, file system, copy/paste, pipes) | + | |
| - | - document or application centric views may be problematic. suggestions; | + | |
| - | - we can see the tools we use as extensions of ourselves (literally) as collaborators, | + | |
| - | - complexity emerges out of interaction and assumptions | + | |
| - | - importance of looking backward as well as forward | + | |
| - | - from mute systems -> conversational systems | + | |
| - | - find ways to make context more apparent. material, ephemera and objects. | + | |
| - | + | ||
| - | + | ||
| - | - 3 stage exercize | + | |
| - | - 1. image selection. "what tool is this?" and "how can this tool work with other tools?" | + | |
| - | - 2. groups ~5. explain each tool in circle, explain how they can work together, single shared metaphor | + | |
| - | - 3. group of representatives of each group. repeat with shared metaphors. | + | |
| - | + | ||
| - | - introduction | + | |
| - | - questions? | + | |