Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revisionLast revisionBoth sides next revision | ||
| project_qfwfq_notes [2011-08-26 11:04] – yaxu | project_qfwfq_notes [2011-11-10 12:41] – davegriffiths | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====Brainstorming space==== | ||
| + | |||
| + | ===Range of interesting technologies=== | ||
| + | |||
| + | * Tangible interface | ||
| + | * Haptic feedback | ||
| + | * Touchscreens | ||
| + | * Keyboard/ | ||
| + | |||
| + | ===Towards Potential concreteness=== | ||
| + | |||
| + | Spreadsheets -> Programmable matter, use cases: | ||
| + | |||
| + | ==Tangible programming for searching open data== | ||
| + | |||
| + | * Human augmented realtime search (over batch mode search) | ||
| + | * Is a change in emphasis (human interaction over raw speed) worth the trade off? | ||
| + | * How can this be realised? | ||
| + | * Interfaces | ||
| + | * Suitible algorithms | ||
| + | * Suitible visualisations | ||
| + | * Going further - realtime modification of (eg. search) algorithms while they are running | ||
| + | * Human shaping/ | ||
| + | * Connection to livecoding | ||
| + | * Collaboration - allowing new levels of engagement with massive datasets by multiple parties | ||
| + | * As a form of conflict resolution | ||
| + | * Performative aspect - Hans Rosling style, but where the algorithms are open to criticism/ | ||
| + | * Public access to data and interpretation | ||
| + | * Fiddle with the interpretations for yourself? | ||
| + | * Online/ | ||
| + | |||
| + | ==" | ||
| + | |||
| + | * Often cited as a problem by many professionals in different areas | ||
| + | * "Used to be able to look at the numbers in a text editor/ | ||
| + | * Already have an intimate knowledge of their data, this is lost with size/" | ||
| + | * Why is this a problem? | ||
| + | * Leads to a loss of control/ | ||
| + | * Need to understand implications of algorithms - perhaps before data is collected | ||
| + | * How can it be solved? | ||
| + | * Psychologically (what is missing?) | ||
| + | * Technically | ||
| + | * How domain specific does the solution need to be, is it generalisable? | ||
| + | |||
| + | ==Understanding of time== | ||
| + | |||
| + | * A problem in social networks | ||
| + | * Implications in other areas | ||
| + | * Use of music | ||
| + | * Human time vs computer time | ||
| + | * Moving between these for tangibility | ||
| + | |||
| + | ==Finding appropriate ways of programming with a limited interface== | ||
| + | |||
| + | * Making phones/ | ||
| + | * Lack of tools in this area is a fundamental problem | ||
| + | * Leads to specialisation of programming, | ||
| + | * Focus on Aakash for example | ||
| + | * Text editors (even with nice features) suck on touch screens | ||
| + | * Perhaps " | ||
| + | * Does this actually require rethink of programming down to language level? | ||
| + | * New language axioms or just representations of eg map/ | ||
| + | * Amorphous programming, | ||
| + | * Is this more suitable framework for less discrete/" | ||
| + | * Multiple levels of process resolution (parallel with overall marshaling - scatter/ | ||
| + | |||
| + | ==Novel approaches to creativity== | ||
| + | |||
| + | * Games as learning environments - well researched area | ||
| + | * Game world as "safe space" for experimentation/ | ||
| + | * Games as ways for people to see things from different perspectives | ||
| + | * "Game programming" | ||
| + | * Current examples lack integration of programming into the game world itself - treated as separate " | ||
| + | * When programming " | ||
| + | * We can make this hack a feature - designed in from the start | ||
| + | * Algorithms as world, processes as agents = very visible/ | ||
| + | * As a solution to algorithmic malleability | ||
| + | * Easy to see whats going wrong and where | ||
| + | * It's realtime | ||
| + | * Games as environments filled with interacting agents (incl humans) | ||
| + | * Human level of understanding, | ||
| + | * Current languages abstract machine process into human level metaphor (for/while loops etc -> assembler) | ||
| + | * Next languages need to also abstract machine time to human understanding? | ||
| + | * Remove the write, compile, run cycle - programming as interaction (see above) | ||
| + | * Debugging techniques | ||
| + | |||
| + | ====Initial 2011 reset==== | ||
| + | |||
| ===Core motivations=== | ===Core motivations=== | ||
| Reasons to reinvigorate qfwfq from a FoAM perspective. | Reasons to reinvigorate qfwfq from a FoAM perspective. | ||
davegriffiths