Effective Django at OSCON Post-Mortem

I’ve been on the road a little more than a week now, back to back conferences. On Tuesday I presented my Effective Django tutorial at OSCON. I’ve recently updated it to cover integrating static assets with your project, and re-organized some of the view information. The biggest challenge with presenting a tutorial like that is figuring out how fast (or slow) to go. I’ve practiced the tutorial and use Django daily, so of course I’m able to type and diagnose what’s going on more quickly. At the break on Tuesday a few people asked me to slow down, but as I walked around the room, two others told me (quite kindly) that they wouldn’t mind if I sped up. This was a little worse than at PyCon, I think, primarily because I didn’t have friends and colleagues assisting me. At PyCon they were able to wander the room and help backfill support for those who were moving a little slower.

I think the next time I deliver Effective Django — or any tutorial — I’ll probably try to mitigate with a few different ways:

  • Make sure I have assistants. I actually had one planned for OSCON, but he unfortunately fell ill. Next time I’ll try to have more than one scheduled (I had four at PyCon, three is probably fine).
  • Provide more guidance in the synopsis. If I’m going to assume no prior Django knowledge, I should probably say something like “We’ll start from zero and build a Django application together,” rather than just relying on the slightly ambiguous Novice tag in the program.
  • Provide some clear stopping points. I noticed that some attendees stayed with it for the first half, or first three quarters, but disengaged before the end. I tried to structure the tutorial so that you can stop at any time and still have learned something, but I could be more explicit about that. “And now we know how to write views that use the ORM,” rather than “We’ll see in a moment how to wire that into the …”
  • Make sure my handouts are ready to go. At OSCON I didn’t realize they were sitting in cardboard boxes off to the side until half way through. I noticed that in the second half, a couple of the people who had been struggling previously were keeping up slightly better once they had another source to refer to.

The people I spoke to afterward uniformly said they learned something (whether it was as much as they’d hoped is another question, I suppose), so this feels like an overall success.

author:Nathan Yergler
tags:oscon, pyohio, effective django, python3

OSCON 2008

I’m in Portland, Oregon this week for OSCON 2008. Asheesh and I are speaking tomorrow on ccREL and `liblicense <http://wiki.creativecommons.org/liblicense>`_.

Things I’m hoping to see this week:

  • lots of attention paid to identi.ca, not just as an alternative to Twitter but as a first step towards truly open services,
  • lots of discussion about how free software can enable user autonomy,
  • corporate suit-types excoriated for not giving back (or for expecting us to build our “open” systems on theirs (I’m looking at you, [STRIKEOUT:Sourceforge 2.0] Atlassian).

So I’m probably just dreaming when it comes to the last one (maybe all of them, particularly with my qualifier of lots), but for the first time in a few years, there are actually talks I want to go to scheduled against one another. Maybe I’ll have to revise Yergler’s Theorem of Conference Value. But probably not.

date:2008-07-23 09:28:43
tags:oscon, oscon2008, portland