248days since
CHI 2009

Recent site activity

Dimensions Group 4

People

  • Ken Arnold
  • Scott Klemmer
  • David De Roure
  • Jill Cao
  • Elizabeth Churchill
  • Hsiang Chang
  • Matthew Webber
<meta topic="What makes a good classification?">
"I love that book, but I've never found any of those dimensions useful."

Gulf of Execution / Gulf of Evaluation illuminates a discussion
purpose of a framework: design? evaluation? does it tell you the context of the problem?
 - sometimes people struggle to shoehorn their work into a framework
what are the attributes of a system that matter?
</meta>


role of failure ("screw-ups")
 - debugging practices
 - what things can be excised and replaced
 - who can remove, fix, replace, etc. roles of people in this.
 - flexibility in the process (anecdote from Japanese process -- it's the relationship between the customer and the organization, losing face)


Community: knowledge / resources:
 - others (community) - "The Angels in the Cloud" (let's write it)
 - known and unknown
 - dependencies (the converse) - what will break you?
 - extensibility: can other people build on it? can they build on each other?
Distinguishes:
 * code in cloud or locally
 * building on others' code?


role of interactivity
 - time to evaluate a change (constant compilation / constant testing)
 - how much are you thinking "with" the system
 - Visual Studio / Flex - flip rapidly between code and layout view - multiple representations - either view can be an evaluation of the other one


role of time?
- how systems change over time



Primarily from scratch, or modding other programs 
 - crowdsourcing / group building (how "Web 2.0")  
 - free updating of dependents / how "living" is your code  
 - code and changs saved in the cloud or local?


user roles: distinction between end user programmers and end user users 


"What did you do?" "Why did you do it?" 
ghost actors

kinds of guarantees
 - keywords and natural language: imprecise, but failure-tolerant, humans in loop
 - traditional programming: stronger guarantees.


reliance on symbolic knowledge

role of expertise

what kinds of exploration are built-in?
 - ability to construct multiple variations
 - "ask me when you get here" / conversationality
  
ambiguity: embraced or squashed out