? = invalid 0 = none 1 = -- 2 = - 3 = # 4 = + 5 = ++The following table summarizes the counts for all Question/Answer pairs (162 = 100%).
+-------+----------+----------+----------+----------+----------+-----+-----+ | Q \ A | 1 (--) | 2 (-) | 3 (#) | 4 (+) | 5 (++) | 0 | ? | +-------+----------+----------+----------+----------+----------+-----+-----+ | PACK | 11 7% | 34 21% | 33 20% | 53 33% | 30 19% | 1 | 0 | | SHOP | 7 4% | 12 7% | 29 18% | 77 48% | 34 21% | 3 | 0 | | PRINT | 61 38% | 38 23% | 27 17% | 15 9% | 16 10% | 4 | 1 | +-------+----------+----------+----------+----------+----------+-----+-----+ | LGAME | 7 4% | 12 7% | 26 16% | 66 41% | 47 29% | 1 | 3 | | RACE | 5 3% | 14 9% | 28 17% | 70 43% | 41 25% | 2 | 2 | | WIRES | 7 4% | 15 9% | 25 15% | 39 24% | 71 44% | 3 | 2 | +-------+----------+----------+----------+----------+----------+-----+-----+ | SHOW | 15 9% | 11 7% | 65 40% | 34 21% | 27 17% | 8 | 2 | | TIM | 6 4% | 6 4% | 40 25% | 46 28% | 58 36% | 6 | 0 | | POC | 4 2% | 2 1% | 19 12% | 40 25% | 91 56% | 5 | 1 | +-------+----------+----------+----------+----------+----------+-----+-----+
The (batch) programming tasks LGAME and RACE of the second day peak at + and the (reactive) programming task WIRES peaks at answer ++.
The auxiliary program SHOW (file viewer) peaks at #, TIM (execution timer) at ++, and POC (program checker) also at ++.
These results should be interpreted with great care. The questions were (necessarily) vague: How much did you like X? It is not clear to what extent a competitor relates the amount of (dis)liking to personal performance on the task or to prior expectations of the task. In particular, it should be noted that for every question, each of the possible answers occurs. For instance, 10% is (in some way) enthousiastic about the theoretical task.