Recently, on “Pi Day” (3.14, or March 14 for the non-nerds out there) I was reading an article about the benefits of learning programming on the Raspberry Pi, a micro-computer that costs only $35 dollars, and all the ways that it helps tinkerers learn programming and solve obscure issues by creating their own software and hardware solutions. I had recently fallen into the trap of tech lust—the feeling nerds get when they suddenly want to buy some piece of technology they may or may not really need—and decided that I wanted to buy a Pi device and get back into programming, having not written a line of code since high school.
That last bit presented a bit of an issue for me, however. Learning to code was always easiest for me when I had a specific issue to solve, since it helped me predict what kind of code I needed to learn, while also making the motivational factor much easier to maintain. It’s this feeling of not knowing where to start that I often see students struggle with as well.
Facing this issue myself, before I decide which Pi to purchase I’ll look online for specific Pi projects that others have done, to see what solutions I may be able to integrate into my own network and test bench at home. At the same time, I think it is helpful to consider the different pedagogical approaches available to instructors to naturally integrate problems into the assignments we give, in order to help students learn to solve them.