Re: Picademy USA - April/May 2016
Good Day Everyone. I looking forward to this weekend. I am excited and nervous at the sametime. Looking forward to me everyone!
Re: Picademy USA - April/May 2016
Getting on board the forum a bit late here. Just drove down from Sebastopol in Sonoma County. Can't wait to meet everyone tomorrow! It sounds like an awesome weekend awaits!
-
EdTechMaker
- Posts: 2
- Joined: Fri Apr 29, 2016 5:27 pm
- Location: New Jersey
- Contact: Website
Re: Picademy USA - April/May 2016
My car was broken into last night and all of my stuff was stolen. I'm going to be a bit late
Dan Borghoff
MakerSpace and Robotics Teacher
Twitter: @EdTechMaker
DanBorghoff@gmail.com
MakerSpace and Robotics Teacher
Twitter: @EdTechMaker
DanBorghoff@gmail.com
Re: Picademy USA - April/May 2016
I just have to say that this last weekend was one of the best events that I have attended. I have so many things that I want to bring to my community now. Just sitting down and mapping out the next year. Hope to see all the great projects that are being done around the world. Thank you again...
Re: Picademy USA - April/May 2016
Still processing this incredible experience. So much to reflect on. Just finished my blog entry about the weekend. Looking forward to staying connected with this community!
Peter Strawn
Robotics Coach - FIRST Team 692
Academic Technology Specialist
Picademy USA - Cohort #2
@strawn_ed
Robotics Coach - FIRST Team 692
Academic Technology Specialist
Picademy USA - Cohort #2
@strawn_ed
Re: Picademy USA - April/May 2016
Greetings,
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.
Dan B
@Dan_Blick
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.
Dan B
@Dan_Blick
-
MattRichardson
- Raspberry Pi Foundation Employee & Forum Moderator
- Posts: 137
- Joined: Sun Oct 07, 2012 3:39 pm
- Location: San Francisco, CA
- Contact: Website
Re: Picademy USA - April/May 2016
Peter and Dan,
Thank you so much sharing your reflections on Picademy! What a delight it is to read these. It's so important to us that everything we talked about and the community that's built carries on beyond the weekend and into the future. I'm getting the feeling that we've achieved that. If there's anything we can do to foster and grow this community, please let us know!
Matt
Thank you so much sharing your reflections on Picademy! What a delight it is to read these. It's so important to us that everything we talked about and the community that's built carries on beyond the weekend and into the future. I'm getting the feeling that we've achieved that. If there's anything we can do to foster and grow this community, please let us know!
Matt