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”:

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.


Popular posts from this blog

Hatchery Program Returns for 2019

PyCon is known around the world as the Python community’s premier event, attracting people from 39 countries. Outside of the main track of talks, PyCon is home to a growing number of events such as Young Coders, the Education Summit, Language Summit, Poster Session, and most recently the PyCon Charlas. The conference strives to be globally representative by promoting diversity and inclusion through these additional events and outreach programs. Our community works to approach these goals year on year. While we regularly receive requests to add events to PyCon, we have not had an established process for accepting and evaluating the community’s suggestions. By introducing the PyCon Hatchery Program in 2018, we took an initial step to introduce a long term process for evolving PyCon. What is our goal?We want to support our community and enable them to add events to PyCon that are important to our community. The long-term goals of this program are to support and grow sustainable programs th…

Pycon 2019 Call for Proposals is Open!

The time is upon us again! PyCon 2019’s Call for Proposals has officially opened for talks, tutorials, posters, education summit presentations, as well as the hatchery program PyCon Charlas. 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.

Please make note of important deadlines for submissions:
Tutorial proposals are due November 26, 2018.Talk, Charlas, Poster, and Education Summit proposals are due January 3, 2019.
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.


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…