# INSTRUCTIONALS» PseudoCODE Drawing

My initial attempt at the instructional drawing was a flop, partly because the outcome drawing wouldn’t necessarily be able to represent what the instructional was instructing was doing and partly because the commands just aren’t easy for a human to execute without being frustrated (myself included) and partly, just being obsessive. Luckily, the ‘failure’ served as a funny sort of re-whipping-into-shape.

During the first attempt, I found myself getting more into the ruler than the pencil. So in my second attempt, I tried to express that idea much more simply, along with implementing a couple simple loops/conditionals that punish the person executing the instructions for giving negative feedback about their user experience [as a computer].

So while my second attempt was under-parameterized, but perhaps more accessible/’interesting,’ my first attempt ended up failing in a very different way, in that it was too time consuming for the human “computers,” highly parameterized, and pretty devoid of interest. But aside from that, writing pseudocode for human computers was just really fun to do.

So I thought I’d share both attempts, if only to show what not to do (at least if you don’t have a reason to).

Second Attempt at Instructional Drawing (the one I actually got people to execute):

###### m6: Please rate the quality of this user experience with a value from 1-9 with 9 being the highest posible rating. Store this number in the variable [value] set the variable [satisfation] = [value] set the value of [satisfaction = x set the counter variable [overyet?] = [overyet? + 1] if [overyet?] > 5 AND [satisfaction] >= 10 stop and quit else start again at the function d(x). return pencil, return ruler

First Attempt at Instructional Drawing (plus some of the other statements I wrote trying to do this at first..)