Skip to main content

Staggering Through PyCon

If you have been looking over the PyCon schedule while packing your bags this weekend, you might have noticed that — besides flat-out offering more talks than any PyCon in world history — this year's schedule has a really interesting feature: the start of lunch time is “staggered”, with some talks ending just after noon at 12:15, and others ending fifteen minutes later at 12:30. The talks that start right after lunch are similarly staggered across fifteen minutes, starting either at 1:20 or 1:35. Just take a look at the schedule and search for the word “lunch”:

http://us.pycon.org/2010/conference/schedule/

If you have ever been at a conference where you had to stand in an enormous line as everyone at the conference tried to get lunch simultaneously, then you probably have an idea about why we are excited about this change! With this staggered arrangement, there should be a shorter line for lunch, since the conference-goers will arrive in two waves.

But the real win is that, for the first time, attending a 45-minute talk will not mean missing two 30-minute talks! For contrast, compare this year's staggered schedule to the 45-minute talks in last year's schedule, which you can see here:


Do you see the difference? Last year, many of the 45-minute talks forced you to miss at least parts of two other 30-minute talks! The staggered schedule eliminates this restriction entirely: because the 45-minute talks carve their extra 15 minutes from unstructured times like lunch and the afternoon break, you never wind up having to choose to see “one talk for the price of two.”

And this additional convenience, we hope, will make it a bit more bearable that you have to choose between such great talks in the first place!

Travel safely, and we look forward to seeing you later this week.

Comments

Popular posts from this blog

PyCon 2018 Code of Conduct Transparency Report

The PyCon Code of Conduct sets standards for how our community interacts with others during the conference. For 2018 the Code of Conduct underwent an extensive overhaul, our procedures for reporting and responding to incidents were improved, and our on-site methods were improved. You can read more about the updates for 2018 here. Cumulatively these changes were meant to improve the safety, welcoming nature, and overall inclusivity of PyCon. Based on initial responses, feedback, and incidents reported this year we feel that we made progress on those goals. A Code of Conduct without appropriate reporting and response procedures is difficult to enforce transparently, and furthermore a lack of transparency in the outcomes of Code of Conduct incidents leaves the community without knowledge of how or if the organizers worked to resolve incidents. With that in mind, we have prepared the following to help the community understand what kind of incidents we received reports about and how the PyCon…

PyCon 2018 Registration is Now Open!

We’re thrilled to announce the opening of registration for PyCon 2018 in Cleveland, Ohio! The prior six PyCons have sold out, so prepare for another one and get your tickets early. The first 800 tickets sold are priced at an early bird discount, saving over 20% on corporate tickets and over 12% on individual tickets. Students save $25 if they purchase early!

To get started, create an account and head to https://us.pycon.org/2018/registration/ to get your tickets!

You get a package that is hard to beat when you register for PyCon. The conference itself is three days worth of our community’s 95 best talks, amazing keynote speakers each morning, and our famed lightning talks to close out each day, but it’s much more than that. It’s having over 3,000 people in one place to learn from and share with. It’s joining a conversation in the hallway with the creators of open source projects. It’s taking yourself from beginner to intermediate, or intermediate to advanced. For some, it’s getting st…

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…