A full week later, after Picademy US #2, I am still processing our work together and what we learned and shared with the amazing team from the Raspberry Pi Foundation. I've not yet converted my swirling thoughts into a blog post but plan to soon. Meanwhile, see Peter Strawn's (@strawn_ed) excellent writeup at https://strawned.wordpress.com/2016/05/ ... ademy-usa/
Of all the technological, computer science, hardware, and code writing parts of the Picademy experience, two other things have really stuck with me. One is how effective real-time, project-based work can be in *groups*
. As a card carrying introvert, I empathize greatly with students who can't stand to work in groups. However, somehow our work as teams in Picademy, centered as it was around our own crowd-sourced ideas for projects (similar to choosing Unconference topics) was highly effective, even given that many of us had never coded or used the Pi before. This (the "capstone" project we collaborated on in teams) of course built on the previous day of skill-building work, also performed in teams, with plenty of "guide on the side" help from Pi staff. The second strong takeaway I'll share, and it's possibly more profound than the first, is how Picademy supported our learning with the space and permission to fail
. As James Robinson and other Pi folks reminded us, another way to view failure during the process of trying something new is as a First Attempt At Learning. The ideas and techniques (and the Pi hardware and software themselves) are very forgiving in this way. Fix it, try it, fix it again. Our experiments in live-coding in Sonic Pi to create, play, and edit music was a fantastic example of this. More to come.