Skip to main content

Interview with tutorial presenter Brandon Rhodes

Last year was a busy one for PyCon tutorial and talk presenter Brandon Rhodes. His conference trips took him from Santa Clara to his home state of Ohio and up to Toronto, with talks at all of them. PyCon was particularly busy with two tutorials as well as two talks, going with single talks at PyOhio and PyCon Canada later in the year. He also made a busy 2011 for himself with three talks at PyOhio in 2011 after his PyCon tutorial, and gave great dictionary talk the year before at PyCon 2010 with the tutorial that started it all. Save for the tutorials, you can check out those presentations on pyvideo.

He’s kicking 2013 off right with a redux of his well received “Documenting Your Project in Sphinx” tutorial, giving its fourth run on Thursday March 14 at 9 AM. Started at PyCon 2010 in Atlanta, the tutorial introduces the widely used Sphinx documentation framework, a staple of the Python community. Sphinx lets you focus on writing great documentation rather than inundating the writer with all sorts of presentation details. The powerful framework is hard at work powering Python’s own documentation at http://docs.python.org/.

Brandon uses a presentation style he dubs “lightning lectures”, where he gives a small lecture on a particular topic, then immediately gets the attendee into an example. New for this year is a streamlining of the exercises, where instead of having attendees make up documentation on the fly, they’re provided with pre-written text, allowing them to focus their efforts on the Sphinx features they just learned.

Two new topics were added for the 2013 edition, both of which are worth the price of admission for anyone getting started towards better documentation. Brandon will be working in some examples of theming to style up your documentation, and deployment to the popular Read The Docs Sphinx hosting service gets some well deserved coverage.

I asked Brandon about the popularity of RTD and its addition to this year’s course, and he was ecstatic to be introducing it. “I think that hosting is only half of the reason for its popularity: the other reason is how simply it integrates into a project's version control system, where commits on GitHub can automatically cause the documentation to be rebuilt on Read The Docs!”

“The tutorial really tries to describe how documentation in text files under version control can integrate with a live project,” he said to describe the course. Organization is key when it comes to documentation, and he covers Sphinx’s layout “in a way that makes sense to people using the library for the first time, as well as for people who are quite experienced with the software but need to look something up.”

He’s also taking the stage for a talk on Friday morning at 10:50, titled “The Naming of Ducks: Where Dynamic Types Meet Smart Conventions”. “I sometimes see snide comments from static language folks about how Python code is unreadable because you never know the types of any of your variables,” he said of how the topic came up. Through this talk he hopes to dispel the unreadability myth by showing the conventions Python programmers use and how they affect the utility of a name. “Variable names in Python are not throw-away; they are our lifeline, that make it possible to read each other's code, and to read our own code months later,” he exclaimed.

Be sure to check out Brandon’s talk on Friday and sign up for his Sphinx tutorial on Thursday at https://us.pycon.org/2013/registration/. Although the conference is sold out, tutorials are still accepting registrations for the low price of $150 per session. That gets you three hours of learning from some of the best educators in the Python world, and includes lunch and a snack break. It’s really worth it, so check out the schedule: https://us.pycon.org/2013/schedule/tutorials/.

Check out what Brandon’s up to on twitter at @brandon_rhodes and take a look at his recent open source project, Skyfield, a really cool astronomy tool. PyCon is happy to have him back again for another year and we hope you enjoy his presentations as well as all of the others on our schedule.

Comments

Popular posts from this blog

Code of Conduct Updates for PyCon 2018

With PyCon 2018 approaching, I’m excited to share some work that the PyCon staff, volunteers, and Python Software Foundation have undertaken in preparation! The Python community and thus the PyCon community is always evolving and growing. In light of this it is crucial that we periodically reconsider and adjust the way that we interact within these communities. In 2012 PyCon adopted a Code of Conduct to foster a more welcoming environment at the conference and provide policies and procedures for addressing violations. Each year since, changes have been adopted to work towards our goal of an enjoyable and fulfilling conference for all attendees. For 2018, we took a larger step and worked with a third party expert fromOtter Techto reevaluate and improve our Code of Conduct, reporting procedures, and staff response procedures. Sage fromOtter Techcame with a resounding recommendation fromNorth Bay Pythonorganizers. In this post, I’d like to summarize the changes we’re bringing this year. If y…

Keep an eye out for the Open Space events at PyCon this year!

These meetup-like events are a great way to learn something new or connect with others who share similar interests. Due to their self-organized nature and the breadth of topics, there is bound to be an Open Space event that can enrich your conference experience. In the past, Open Spaces have included a wide range of topics such as natural language processing, web frameworks, yoga, and playing board games. Any topic that two or more attendees are interested in could be a good candidate for an Open Space.

Open Spaces are held during the three main conference days in meeting rooms reserved for these events. Any attendee can create an Open Space event and reserve a room by adding a card to the Open Spaces boards found near the registration desk. Checking these boards regularly during the conference, subscribing to the hashtag #PyConOpenSpace, and following @openspacesbot on Twitter are ways to keep informed about upcoming Open Spaces.

Promoting your Open Space 
If you decide to host your …

How & why cities and dates are selected for Pycon

Foreword from the Chair: The PyCon staff, volunteers, tutorial presenters, speakers, poster presenters, and community members have been hard at work preparing for PyCon 2018 in Cleveland, Ohio. Along the way, we’ve gotten a chance to have some solid discussions about what makes PyCon good as well as where it can improve.

In February one of those discussions was around the dates when PyCon 2018 will be occurring, specifically the conflict with Mother’s Day 2018. The outcome of that discussion was a commitment by the PyCon staff to better communicate what decisions and compromises were made along the way and how they were considered.

PyCon is run by the Python Software Foundation, which is a grant giving non-profit. Many misunderstand or are unaware of this relationship, but the Python Software Foundation relies on maintaining a strict budget for the operation of PyCon in order to continue its grants programs and other financial responsibilities.

The PyCon staff and Python Software Foundat…