Wednesday Weekly Wisdom #2: Who are you people?

Welcome to Wednesday Weekly Wisdom. Click here for background on what I mean, or read last week’s post here

I want to start this week by addressing a feeling that many of you are probably having with regards to your teaching team – the feeling of not really knowing anyone. Especially for first year volunteers, it’s not uncommon to still feel like someone on the outside looking in.

If you were lucky, you met your team (or at least a few members) at the first in person training. You’ve hopefully started having conference calls, though, they’ve either been basic intros or discussions about the classroom plan. Many of you still only know each other through the internet. And many of your teammates work in different places for different companies, so meeting up is a luxury.

It’s ok! These feelings are normal, and you are not alone. If you don’t know someone on your team, they also don’t know you, and nearly every team is in the same place.

However, as a remote team, this is not a problem that will solve itself. Remote teams don’t have the chance to have the casual, face to face conversations that build teamship. You don’t have 5 minutes before class to chat or a carpool ride to catch up. You handoff plan is an online shared document, your chit-chat is audio/visual testing before class starts, and your team meetings are all virtual.

Remote teaching is incredible, but it also easily leads to getting through most of a year, looking around, and still thinking, “who are these people?”

It’s worth figuring out how your team will build a sense of teamship. The better you know each other, the better you’ll operate better as a unit. You’ll also have an easier time calling out problems and disagreeing (constructively) with one another – both of which are critical to success. And, if your team hasn’t communicated at all yet, it’s past time! It’s ok for anyone to send that first (or second, or third) email to the team. If you feel like you need more communication, communicate more! And if you’re having trouble reaching people, including your classroom teacher, leverage your Regional Manager – they’re there to help you succeed!

So, find some time to bond. If you’re lucky enough to work close to each other, have you weekly sync calls in person, and call the classroom teacher together. If you’re a little more spread out, find the time every so often to get together. A team breakfast or lunch not even once a month goes a long way. Last year, my time got breakfast once about every six weeks, and even the people who dined solely on coffee would come and enjoy having a chance catch up. If nothing else, plan your school visits together! You’ll likely have a couple hours of travel time, or at the very least, will get most of a day in person together. And if that is truly the only way to see each other, then it is a good use of time, even if you’re tempted to spread out your visits.

Right now, you’re called a team. Soon, you’ll be teaching together as a team. And with a little effort, you can be feeling like a team in no time.

Wednesday Weekly Wisdom #1: You’re Cooler Than You Think

As a part of my volunteering with TEALS, I’m writing a weekly blog for new remote education volunteers. See the tag “weekly wisdom” for other of these posts


Kicking off this idea of “weekly wisdom”, I want to start with one of those concepts that doesn’t really get covered in a training, and one that took a while for me to learn:

As a remote volunteer, you’re cooler than you think.

This is especially true for those of you who, like me, are volunteering with a rural school. Think about it from your students’ perspective – you are a professional, working in a field that your students are only just starting to learn. And you’re not just some guest speaker that will come in for a day and then never be seen again. You are stepping into their lives day after day for an entire year. They’ll get time to get to know you, get comfortable with you, and seek mentorship from you, in a way that they often are otherwise unable to get.

Taking it a step further – you are an incredible asset for your entire school. If you’re willing and able to put in the time, a visit to your classroom can be transformative not just for your students, but other classrooms as well. During trips to our school, we spend the entire day meeting not just with our TEALS class, but with the other tech classes, helping give deeper meaning to what they’re learning in courses from web design to basic computer use.

We also use one trip a year to drop in to some of the non-tech courses. We talk to the marketing class about how market research impacts the features we write and when we write them. We talk to the graphic design class about how our designers play a critical role in defining what our product is and how it makes users feel. We show these students how their work and interests combine with technology. And at the same time, these visits build bonds between our new CS program and other teachers, and build interest in TEALS courses in other students.

As you plan for the year, and plan for your visits, plan to leverage how unique TEALS is. Take your cool factor and invest it around not only your classroom, but your entire school. The benefits will come back tenfold.

From TEALS: Wednesday Weekly Wisdom #0

As a part of my volunteering with TEALS, I do most of my teaching remotely, communicated with my class via Skype. Despite large advances in technology, remote education is still a small field, and so the experienced remote instruction volunteers with TEALS are uniquely equipped to help prepare new volunteers.

As a part of this, I’ve started a weekly blog, aimed at covering topics that I feel new volunteers should know, and that are typically not covered during training sessions. I’m reblogging them here, all with the “weekly wisdom” tag, in case they’re of any use or interest to you, my loyal readers. Below is my introductory post, and the rest will come across the summer.



Hey remote volunteers!

My name is Matt, and I’m entering my third year of remote teaching with TEALS. In the past couple of years of volunteering, I’ve learned a lot about how remote education works. As a returning volunteer, I sometimes get asked to share some of the things I’ve learned, especially with the huge growth in new remote volunteers joining the effort.

I’m going to start some weekly posting on remote education practices or concepts that I think are important. If you’re a new volunteer, I hope you find them helpful, and if you’re an experienced volunteer, I’d love to hear about your experiences on the topic – I’m still learning too!

A lot of my experience relates to rural schools, but I hope the ideas are generally applicable. If you have a question to ask or an experience to share, leave a comment or start a new topic! Exchanging ideas helps everyone 🙂

Powered Down



How technology education clashes with basic student needs – and leaves the most in need behind.

The integration of technology into schools across the country is growing, and creating incredible new opportunities for students to learn and broaden their horizons. Tech is transforming schools. With new opportunities, however, come new problems. For example, I’m teaching computer science to a group of high school students, nearly half of whom do not have access to a computer outside of school. Assigning homework that requires a computer would be giving those students work that they cannot possibly complete at home. And this is in a course that teaches them to program computers!

A growing number of schools are fortunate enough to have funding to implement “one laptop per child” policies, giving students a computer that they are often allowed to take home with them. The next step in that progression is to expand internet access, so that those students can get online at home as well. Amazing progress has been made against these issues: according to a 2015 Gallup/Google survey, 91% of students report having a computer at home that has access to the internet[1]. In terms of tech education, this creates powerful learning opportunities for students.

Except for when it doesn’t.

I recently participated in a Twitter chat focused on technology education in rural schools (#ruraledchat). One of the discussion topics was about struggles in planning technology based assignments when students have neither computer nor internet access at home, which I’m familiar with. One teacher’s follow-up, however, caught me completely off guard:



Tammy G Neil: “Since my entire curriculum is online, I have to take into account those without access at home. It’s sometimes a struggle.”

Elizabeth Hill: “Do you have any easy to share suggestions about that? my district is going 1:1 and some of my Ss don’t have electricity…”


To hammer that home: this teacher’s struggle with planning tech lessons was that some of her students lack electricity.

This floored me. I had never stopped to consider the challenge posed by the lack of electricity. Setting aside all of the struggles of simply living a life as a student without power, it poses a near total barrier to home technology access. In the  best case scenario, the ability to complete an assignment becomes a race against the battery capacity of the school provided laptop, and it clearly gets much worse from there. The top question invading my mind was, simply, how many students are affected by this? Is a lack of electricity a widespread barrier to technology education? I dove into the facts to find out.

Or at least, I attempted to. The first thing I found is that there nobody really knows how many families in the US lack access to electricity. Some sources cite that 100% of US families have access[2], but this is demonstrably false. Lacking direct data, I turned to a few other sources to try to narrow in on an approximation. Helping place an upper bound is the Gallup/Google survey above. If 91% of students surveyed report having a computer with internet access at home, then absolutely no more than 9% lack electricity – and probably many fewer, given the multitude of other reasons that a home may lack a computer or internet access.

Trying to drill in to that 9%, the best stand-in I could find for living situation was data about student homelessness. The McKinney-Vento Actdefines, among other things, how schools have to count and handle homeless students[3]. Homeless students are not the only ones without power, but it provides a decent proxy. While the numbers are generally accurate, they may be low, as two issues are known to cause underreporting: first, that students who are homeless often do not self-identify, which is a major way of finding them, and second, that when identified as homeless, students will state that they have greater accommodations than they do. Being able to complete your tech homework when you’re homeless ranks low on the list of concerns in life, but that only drives home the point about the limits of technology.

Now, the numbers: the Department of Education reports that in the 2014-15 school year, the latest for which data is available, there were 1,290,649 homeless students in the US, which is a little under 3% of all students[4]. This definition of homelessness, however, encompasses a broad range of living situations. Some might have reliable access to electricity, such as those who live in motels or are “doubled up”, living in someone else’s home with them. Others, like those who spend their nights in homeless shelters, may have less consistent access to an electric socket from which to make use of their tech.

What’s more certain, however, is that a subset of this population will have little to no outside access to the power grid. They are the 40,306 students who fall into the category of “unsheltered homeless”, and they’ll spend a majority of their nights in parks, abandoned buildings, or similar places. What I find most astonishing about this group is the fact that, despite these circumstances, they manage to remain enrolled in school at all. The only positive aspect about this number is that it is a smaller percentage of the overall student population, coming in at under one half of one percent.

But it’s uncertain yet in which direction these numbers are headed. Even as the economy recovered from the great recession of 2008-2009, the number of homeless students grew, reaching a record high for the 2013-14 school year, and then falling only slightly[4],[5].

When we talk about helping students learn so they can live better lives, this is the group most in need of that help. And yet, the tools and technology meant to help all students learn has little hope of helping them. Like many cases, helping “all” really means “most”. This creates a tough balancing act for teachers and schools looking to increase the role of tech in the classroom, and it’s a balancing act I was hardly considering. How can we design technology oriented lessons that make no assumption about the students’ home resources? Can we even do that, and if we can, how good can those lessons be? How should we balance the fact that by using tech to improve some students’ education, we might be taking our most in need students and isolating them even further?

In the larger scheme of things, is it possible to solve this problem closer to its root? The “free and reduced lunch” program uses existing school infrastructure to offer students who would otherwise go hungry an opportunity for breakfast and lunch, under the guiding principle that lacking food is a major barrier to learning. Could we leverage school infrastructure in a similar way to provide students with greater access to electricity and internet access outside of the confines of class time?

I like to try to end my posts with a nice “lessons learned” section, but in this case, I’m overwhelmed. Perhaps the biggest takeaway is internalizing words I’ve heard before, but never felt as deeply as I do now:

“When we complain about how hard some kids are to teach, think about how hard some of their lives are to live”




Banner image courtesy of Wikimedia Commons and used under the Creative Commons license.

Admitting Mistakes 2

Following up on an earlier post, I’m going to dedicate some more time to take advantage of the fact that I can freely talk about my mistakes as an educator, and talk about another time where things just went wrong. This one is a bit larger of a thing gone wrong, so it will require some background.

In the fall of 2015, I joined a wonderful group of people as a member of a TEALS teaching team. Our team was to help teach an intro to CS course for a class of high school students. The curriculum was largely provided by TEALS, and it been used fairly widely for years, with numerous tweaks along the way.

We were given a semester long curriculum, and one written by bunch of pros at that. Naturally, we then spent the semester teaching the course as written.

At the end of the semester, I took on the responsibility of being the primary grader for the final project. Students had to build the game “hangman”, and it was a great capstone, covering just about every concept and programming structure taught across the semester. We gave plenty of time to work on the project, and checked in with students frequently, so we were generally optimistic about how the grades would come out. Even though some of the smaller assignments had recently been a little rough, we had made sure to cover the common issues and solutions, so we weren’t concerned.

You all probably see where this is headed. Grading the assignment was terribly difficult. Nearly every student struggled with some portion of it. There were some items on the rubric that just about nobody got. Concepts that we thought we had reviewed well were totally and completely misapplied. Lacking understanding, many students found ways to follow the letter of the law of the rubric, even when it meant going out of their way to do something wrong.

How did so many of our students get to the end of the semester with such a misunderstanding of what we had been teaching? What the heck went wrong?

It didn’t take us too long to agree on the first one – in teaching the course as written, we erred on the side of following the curriculum, not of following our students. While we adjusted little bits and pieces of the material, and would slow down or speed up instruction slightly, our main focus was on making sure we covered the entire semester’s worth of material in our semesters worth of time. That caused us to miss the fact that the course as written was really more than one semester’s worth of learning for our class.

Figuring out how to correct that mistake is what led us to understanding the more fundamental one we had made: following other people’s definitions for what success looks like in our own classroom. We had the incredible gift of teaching an introductory course that didn’t end with a standardized test. The only thing that mattered is that our students learned some computer science while taking our course. We could extend, pivot, re-write, or totally trash any of our lesson plans at any point to achieve that goal. When planning and teaching the next semester, we fully embraced that freedom.

The end result? A class full of students that had fun every day, and who connected far more deeply with the material than the first time around. And some truly fantastic final projects.

Lessons learned:

“every classroom is different” isn’t just a true statement, it’s a fundamental truth about education. It does more than suggest that even the best curriculum be adapted different each time, it requires that adaptation.

More importantly, when striving to succeed, the first step is to be deliberate in defining success.