I hadn’t programmed since 1992, and even then I was just a second-year college student who wasn’t anything special when it came to coding. If I remember correctly, we were using something like Pascal, and then we dabbled a little in Assembly language. But that was almost 20 years in the past, and I hadn’t touched anything to do with programming since. How in the world was I going to launch a high school app programming class for Apple’s iOS?
I started the old-fashioned way: I bought a few books. Luckily, I had a colleague who was interested, so he bought some of the same books, and we occasionally met and talked shop. This was during the 2010-11 school year, and I was slated to offer our new programming elective during the next school year. As with most people, I got busy with work, my colleague got busy with work and family, and in the end, we made very little progress. But then I stumbled upon iTunesU and the Stanford app programming course.
Stanford had begun offering classes for iOS programming back in 2008, and because of iTunesU, those courses were now accessible, and free! I started to watch the material, while trying to perform the exercises. Paul Hegarty soon became my favorite instructor. As great as the material was, I was still having difficulty, because this was not an entry-level course, and my hiatus from computer programming had created a knowledge gap that was a necessary prerequisite to the course material. Nonetheless, I pushed forward and struggled with the material as best I could. Perhaps the greatest impediment was that I was working a more than full-time job as the iPad integration coordinator at Monte Vista already, and so the time I devoted to learning how to code was too sporadic—necessitating a re-learning cycle of already covered material at each sitting.
The next school year was upon me, and I found myself surrounded by 21 eager high schoolers, ready to create the next Angry Birds. My intent hadn’t changed. I still wanted this class to be a practical one, where students would form development teams and then develop an app that met the needs of a particular staff member. I decided I would spend the first semester teaching students how to code Objective-C with Xcode, and then in the second semester, I would put the students into development teams, canvas the staff for app ideas, and then marry up my teams with a particular idea. The major flaw in this plan was that I wasn’t able to code Objective-C myself—at least not yet.
So, I struggled my way through, with a little help along the way. For example, while attending the CETPA conference in November 2011, I met with an Apple presenter who wowed the crowd by creating an impressive app, from scratch, in about eight minutes. His name was Steve Hayman, and he was awesome, not to mention a fellow Canadian. He also sent me his sample code that he used during his presentation, which I then used with my students. But my approach to that first semester is something I like to explain in terms of a Lego metaphor.
- If we’re not measuring AI’s impact on students, what are we measuring? - November 20, 2026
- Sometimes, succeeding in high school takes longer than four years - November 19, 2026
- Teachers spend 8 hours a week supporting student well-being - November 18, 2026
Comments are closed.