CSA chair's connection field trip

I had the pleasure of meeting and talking with CS&E's Distinguished Alumnus, Rebecca Schatz (founder of 'The Works' and leads CodeSavvy.org), about her connecting with kids through coding and the outcomes she has witnessed.  I was personally convinced that CodeSavvy could be that extra-special connection and relationship that CSA has been seeking to bolster our outreach activity.

Rebecca is a terrific role model, fabulous leader and a strong advocate for volunteering with a purpose. She saw 'the need' before it was on most people's 'needs' radar. She experimented and built and tested and proved efficacy and feasibility.  No doubt about it - I was sold!  But, a nano-dilemma presented itself. If 'I' was going to stand behind this, recommend this initiative to CSA and the department, promote it, and do my level best to persuade colleagues, cajole friends and their colleagues to join this movement - I needed to see it 'in action' for myself.  I had to 'eat my own dog food' and see if a) these events were any good; and b) I - as a gray haired, 30 year info pro - could do this and like it!  So, I got the sign-up URL from Rebecca and attended the January 25th CoderDoJo Twin Cities event that CodeSavvy sponsors along with a couple of local software enterprises: Clockwork Active Media and Code42; a well known advertising agency - Colle+McVoy; and a couple of 'like-minded', non-profit, STEM advocates: Good 'n Nerdy and MinnWebCon.


The events are held regularly at the STSS building on the UofM east bank campus. I went as an invited guest - an observer - with a simple plan. I wanted to get a feel for the level and capabilities of the organization and experience a CoderDoJo 'session'. I hoped to spend as much time during the two hour session wandering about talking with the kids in the different code groups, their parents and the 'veteran' mentors.

In the STSS lobby area there were people gathered around a registration table setup adjacent to the entrance of the session rooms. After greeting some familiar folks and registering, I entered the first room and scanned the 'code group' ID placards on each of the dozen or so tables. Mentors, kids and parents were huddled at the respective group tables spread across the expansive room setting up the donated laptops, their own computers and getting their projects going.

Other energetic, young adults were attending to the ever present technical glitches and startup issues like getting the right WiFi password and updating a newly donated laptop's software.
Nearest the door were five or more tables for the 'Scratch' and 'Ruby' groups and farther away a couple of Python and Minecraft tables, At the end of the room there were a couple of Linux groups, Aurdino groups, and a Web Development table or two. Throughout my visit and walkabout, the room was "a jumpin''' with eager minds and bodies in motion. I stepped out to peek into the adjoining meeting/session room and saw another dozen tables filled with eager, energetic experimenters and coaches. The fact finding had begun.

As an 'observer' I was assigned to shadow a 'seasoned' mentor working in the 'Scratch' code group. I took an open seat at a 'Scratch' group table with three 10 year olds and a couple of parents. Other parents were parked nearby observing and waving encouragement to their kids, some were fixed focused, head down and deeply gazing into their smartphone screens, and still others (with kids > 13 y.o.) were off to the nearby coffee shop or the art museum.

As soon as everything was operational at out table, the lead mentor started off with a few questions to get to know the kids and what they were interested in and if there was anything specific they wanted to do. Before I knew it, I was soon as 'into it' and engaged as the kids were in learning 'Scratch' (and it's IDE).

After a couple of exercises were under our belts and we had hit a good stride, our mentor was called away [he was the on-site WiFi and hardware guru] to deal with some hardware problems. Standing up, he turned and tossed the 'Scratch' manual to me saying, "You're on! You are now a 'Scratch mentor'. I gotta go fix that that...." His voice trailing off as and the din of the room masking his words. After a few very, very long seconds of panic and terror I managed to mentally reset and soon I was back; fully engaged with these 10 year olds as we continued their exploration and first experiences with 'Scratch'. It was entertaining, challenging and very rewarding.

We talked about putting a 'Scratch' program together and how they'd go about it. We talked about creating and writing the instructions and then how to 'debug' their code. We joked about doing the same thing over and over and being frustrated and that led to a discussion on how to 'stay in charge' and create a new approach, a new solution to a vexing problem. The kids seemed to have a really good time, and so did those parents who worked alongside their kids. As for me, I learned a lot about 'Scratch'. This was my very first exposure to it.

The 'official' Scratch mentor did return from his errand and I was able to excuse myself and continue my 'fact finding' and 'experiential' walkabout mission at a CoderDoJo Twin Cities event. There was an air of joy and excitement. It was most certainly an energetic setting but it was never chaotic; a paradoxical atmosphere - vibrant tranquility.

As I visited with various groups, I was pleasantly surprised at the number of parents who joined in with their kids learning, experimenting, creating and collaborating. Many of the mentors who I conversed with told me they got involved because of their own children.

At the January 25th session there were at least 100 kids who were therer having a great time. I was told that another 25 or more were on the waiting list and couldn't participate only because there weren't enough mentors who signed up for this session.

It was an afternoon that flew by and  after the event, Rebecca and I only had a few minutes to talk. I asked about the 3:1 student-to-mentor model, and their mentor vetting and training processes. She said that over the years, they've learned plenty about what works with kids and what doesn't. And the same is true in the area of guiding, directing and preparing 'new' volunteers for their 'new' mentoring and coaching roles. Plus, Rebecca said that CSA members will appreciate that these programs are about goals, planning, learning, failing, overcoming, understanding, wonder and the joy that comes with a wonderful outcome.

After my sample of  one event - I can say unequivocally, that I believe CSA should partner with CodeSavvy & CoderDoJoTC! I can strongly recommend and encourage that CSA members become mentors and commit some 20+ hours over a year to a CoderDoJo season and chapter.

The friendship building, networking and new learning opportunities alone make this opportunity personally and professionally worthwhile. The time spent with the kids exploring their ideas and dreams is very rewarding and invigorating. The programs are established, well structured and proven effective. Plus, they are easy as can be for CSA members, friends and colleagues to get in and to stay involved with. The outcomes benefit the kids, the mentors and the community. Volunteer now for this very important work that not everyone can do. There is an unmet need and we're asking you to step up and help us meet it.

CodeSavvy & CoderDoJoTC have already created a model that is pragmatic, personable and professional. It gets to the core of effectively contributing one's time and sharing knowledge and helpful experiences.

They have a vetting and training process in place to help newcomers ease into mentoring or coaching a few young, energetic minds. And from my viewpoint as a grandfather, it was so warm and rewarding to see these mentors (mostly Dads and a fewer number of Moms [all in their 30s, mostly]) working with the kids and honing their teaching skills. It was fun to see rapport and confidence being built by them revealing a programming trick or two. There is plenty of learning and networking opportunities for the mentors, too.

It was very good afternoon. I must’ve thought so, because I signed up for the next session on March 8th. And, I am planning on being at the session after that on March 22nd, and the one after that, too!  I hope and trust more CSA folks will be joining me at future events. It's easy to sign up. Point your browser to CoderDoJoTC.org, check it out and don't forget to signup.   BTW, you'll also find a post below from the co-founder of the CoderDoJo Twin Cities chapter, Matt Gray of Clockwork Active Media. There's a link for you to click on to 'sign up', too! Hmmm, Imagine that!  And Matt will be joining us at the next CSA 'breakfast' meeting in April.

Cheers, John L. Borowicz, CSA Chair 2014
Submitted on February 26, 2014