@@ -5,7 +5,7 @@ After a short introduction to the Micro:BIT (MB), we were told to get familiar w
## The Micro:BIT as a physical object
Our first focus was the Micro:BIT’s tangibility and feel. Since the Micro:BIT is made for learning, the fact that it’s physical appearance is tangible is very important. That the object itself is easy to grasp will make it easier for youths, without hardware and programming knowledge, to understand. When we picked up the Micro:BIT we all drew a parallel to the game boy - the a and b button (as seen on picture 1, the a & b button on the right side) intrigued us to click them, to see what they did. This perceived affordance was perfect for people our age, though we do worry, that the youth wont have the same perceived affordance, because technology today often features touchscreens for interaction.
Our first focus was the Micro:BIT’s tangibility and feel. Since the Micro:BIT is made for learning, the fact that it’s physical appearance is tangible is very important. That the object itself is easy to grasp will make it easier for youths, without hardware and programming knowledge, to understand. When we picked up the Micro:BIT we all drew a parallel to the Game Boy - the a and b button (as seen on picture 1, the a & b button on the right side) intrigued us to click them, to see what they did. This perceived affordance was perfect for people our age, though we do worry, that the youth wont have the same perceived affordance, because technology today often features touchscreens for interaction.
*picture 1 - Game boy*
...
...
@@ -19,4 +19,7 @@ The software used for creating programs for your Micro:BIT as a whole worked gre
The emulated Micro:BIT inside the software gave us mixed feelings. While it was very convenient being able to see how the code was going to function directly in the software, it also left the physical Micro:BIT out of focus.
In addition to these things, the software did a fairly good job of explaining what was actually going on, often with good explanations of both the code and the editor - though we feel that some things might benefit from a general explanation, I.e. the way a boolean is described.
\ No newline at end of file
In addition to these things, the software did a fairly good job of explaining what was actually going on, often with good explanations of both the code and the editor - though we feel that some things might benefit from a general explanation, I.e. the way a boolean is described.
### Henrik comments ###
Nice summary and good connection to the literature. Consider adding a section with the references and/or use hyperlinks directly to the papers references.
