My name is Robert, I am a 24-year-old interaction designer and currently researching designer-oriented programming languages and paradigms for my graduation at the Delft University of Technology. 
contact:  r.a.paauwe@ax38.org
resume: download
/witch doctor mask construction
Notes, April 24, 2012
/24 thesis graphics
Notes, April 19, 2012
/draft code vocabulary 
A first draft of a code dictionary / vocabulary / thesaurus. This is a first visual draft of a timer sample in Arduino, separated between code, control flow and data flow. The hypothesis is that a dictionary of patterns would help interaction designers to assemble their programs. 
Notes, March 27, 2012
/Code Companion Mk.I
An intermediate result of my research. The Code Companion (CC) is a paper tool to help with programming and bridge the gap between idea and code. The Code Companion is essentially a white sheet of A3 with separate areas for different code elements, also see below. The steps of the code companion are based upon a model distilled from designers, as a previous part of my research. 
Step 1 - Inputs & Outputs:The first step is to determine the input(s) and output(s) of the code. Which value(s) and/or behavior(s) do you begin with? Which ones are the result of your code? Think about numerical values, actions required for the sensor to registrate and actuator actions as possible inputs and outputs.
For example: A touch sensitive lamp might have touch intensity as an input and brightness of the lamp as an output.
Step 2 - Tools:The second step is to determine the tools required to get from input to output. Transformers are tools that alter, add, subtract or generally change data & memory items. Conditions are tools that determine when actions or tools occur. Finally, data and memory are storage tools that contain information that might be altered in one way or another through transformers.  
Example:  “touch intensity ”and “brightness” might both be data tools. “Compare-and-change” might be a transformer that turns touch intensity into brightness and finally “after 10 seconds of touch” might be a condition tool that determines when something happens.
Step 3 - Path:After determining begin and end conditions, and imagining the tools required, use them to sketch out the path between start and end. This path is effectively what will be formalized in the computer by programming. The path is what will help you define how the idea should be translated into computer readable code. 
During the sketching process, or during programming,  tools could be missing or not defined yet, one can always evaluate and revise the tool list to keep the model updated. 
Example: An example can be seen below and in large here.
The Code Companion is a tool that forces novice programmers to think in the ways of the machine, before immediately beginning to program. The CC should be used before programming, but after the idea has been created. Even without programming knowledge, this structured approa