Skip to main content

Part 5: Tutorials (PyCon 2008 Chairman's Report)

PyCon 2008 had 28 tutorials in three sessions (morning, afternoon, and evening) on Thursday March 13. Over 420 people attended, more than the total attendance of PyCon 2006. Almost all of the tutorials were full. More than half of the attendees took 3 tutorials, resulting in a very full day for many people. I'm sure more people would have taken more tutorials if they hadn't filled up.

We were using the ten largest breakout rooms, in the lower level of the hotel. They were of different sizes. The five largest rooms could handle up to 70 - 90 people, according to the hotel's capacity chart. We limited registration to 50 in these rooms. The other rooms could handle anywhere from 18 to 36 people. We limited registration in these rooms too, cutting about 20% off the maximum, to allow for elbow room.

It's a good thing we set these limits, because the hotel capacity charts leave out one crucial detail: the maximum capacities listed are for a room crammed full of tables, with no space for the instructor! I suppose if they're running some test like the SATs, they could actually fit that many people. But we needed room for the instructors.

During registration, Greg Lindstrom (the tutorial coordinator) and I watched the tutorial numbers carefully, assigning tutorials to rooms as soon as they (or other) tutorials reached certain numbers. This worked well enough, although it was a bit nerve-wracking. It would be nice to automate the process next year -- but a logic error could have serious consequences.

On Tutorial Thursday the wireless network didn't work. I wrote about it in part 3, and Sean Reifschneider's report goes into detail. The result was that students weren't able to get access to the internet, which was a requirement for many tutorials. Next year, we will have wired ports available in the classrooms, so even if the wireless fails we'll have a backup plan. That was lacking this year.

Once the lack of wireless was worked around, the tutorials themselves seemed to go well. We had enough people taking tutorials that our overhead was more than covered, and we were able to offer dinner as well as the expected lunch.

By the evening session I could see weariness set in. 9 hours of learning (12.5 if you include breaks) is a long time. Next year, maybe we'll try two days of tutorials, either both before the conference, or one day on either side (one coinciding with the first day of sprints). What do you think? This is another topic we're discussing on the pycon-organizers mailing list.

I taught two tutorials myself, wxPython I & II (afternoon & evening). I underestimated the amount of free time I would have to prepare in the weeks & months leading up to PyCon, so I was not really ready. The first tutorial was about 3/4 prepared (although there was no handout). For the last part of the first tutorial and for the entire second tutorial I did code walkthroughs and Q&A. The second tutorial became a "master class". I hope it was worthwhile to attendees, and I apologize for being underprepared.

Next year, I vow not to present any tutorials or talks beyond my duties as chairman. If I start to indicate a desire to present something, please direct me to this post.


Popular posts from this blog

PyCon 2018 Call for Proposals is Open!

It’s here! PyCon 2018’s Call for Proposals has officially opened for talks, tutorials, posters, and education summit presentations. PyCon is made by you, so we need you to share what you’re working on, how you’re working on it, what you’ve learned, what you’re learning, and so much more.

Before we dive in, the deadlines:
Tutorial proposals are due November 24, 2017.Talk, Poster, and Education Summit proposals are due January 3, 2018.Who should write a proposal? Everyone!

If you’re reading this post, you should write a proposal. PyCon is about uniting and building the Python community, and we won’t advance as an open community if we’re not open with each other about what we’ve learned throughout our time in it. It isn’t about being the smartest one in the room, so we don’t just pick all of the expert talks. It’s about helping everyone move together. “A rising tide lifts all boats,” if you will.

We need beginner, intermediate, and advanced proposals on all sorts of topics. We also need b…

PyCon 2018 Launches New Site, Sponsorship Search

After two great years in Portland, PyCon is shipping off to Cleveland for the 2018 and 2019 renditions of the Python community's largest gathering. PyCon 2018 will take place May 9 through 17 with two days of tutorials, three days of talks, and four days of development sprints.

For more information, check out our newly refreshed website at and follow us here on the blog and at @pycon on Twitter.

New Website

The new site features a design centered on the historic landmark Terminal Tower, a 52 story skyscraper that overlooks downtown Cleveland. When it opened in 1930, the tower was the fourth tallest building in the world and the tallest building outside of New York City. Though its height no longer tops the charts, the tower and surrounding Tower City area remain highly important to the city. What once was a beacon to guide ship captains to Cleveland's port and airplane pilots to its airport, the tower now includes 508 LEDs that light up for the holida…

How to get ready for the PyCon development sprints

[A guest post by Kushal Das, one of the 2016 Sprint Coordinators]So — you have already decided to join in the PyCon development sprints! The sprints run for four days, from Thursday to Sunday after the conference. You do not have to be registered for the conference to attend the sprints! Some teams plan to write code over all four days, while some projects plan a shorter sprint if the organizers cannot stay for all four days.Can you start getting prepared for the sprint ahead of time? Yes!There are several things you can do ahead of time, that can save effort once you arrive at the sprints — and some preparations can even be made at home, before you arrive at PyCon:Have your operating system updated and patched — whether Mac, Windows, or Linux. This eliminates one possible source of problems with getting software up and running.Go ahead and install the version control system that will be used by the projects you are interested in. If you install both git and Mercurial on your computer…