Workshop 1.5 + Overall evaluation

This is the evaluation of the first workshop combined with the 1.5 workshop (its .5 because it wasn't a full class and I splited the class in half which I shouldn't have done) 

​This picture was taken by Oliver Dykes. You can see me in the background

​This picture was taken by Oliver Dykes. You can see me in the background

Many things went wrong in the workshop.

The main problem was that I assumed too many things.

First, I did not take in account that most of them were new and I rushed through all the necessary step (I also thought that it takes too much time, I was wrong). I felt now that it is very necessary to go through the structure of the coding very slowly as well as explaining it physically and visually ​as much as possible. I should leave the Arduino almost at the very end after I laid out all the ground work. 

Second, Understanding the structure should becomes my main priority now as there are many unknown the first time you code. The structure of the function should be explained first and in a very clear way. 

void setup() {


}

void loop(){


}

I will try to use more analog example for this so that everything looks like it needed to be contain inside the {              }  ​

​Third, I divided the class up into two groups which is the 'tutorial' and the 'helper' group. I ended up teaching the 'tutorial' group and leave the 'helper' group behind. I should run a separate class for each of these so that I can focus all my time on just helping or teaching but not both. 

Fourth, I should prepare the way I teach electronic. Since most of time wont have the time to work on the same thing. Each of the component then should be presented and prepared before. Letting them search on google is not the best way as the coding are generally, confusing and not necessary. 

The worksheet works out quite well. However, there are always rooms for improvement. The introduction of each tools can be swapped so that the order works. I will give it a go at today workshop. (Tues 5th March). ​

​The overall result is still positive. I think what I have learn so far is that there is a need that people wanted to be able to code and but not able to do them properly (Lack of knowledge etc..). For them to be able to do make functional prototyping properly all stages must be introduced. Its not just having an idea and senario and you can start prototyping. All possible outcomes must be considered before making the prototype. Thus, a tools kit must be used to help a designer to define their idea. Once they managed to have all the detail laid out step by step that is precise enough, the designer can then move on to construct the hardware. The 'coding' or 'programming' then comes at the end.