Skip to main content

PyCarolinas 2012 Recap

I ran a conference.

I said it had to be done, apparently I said I'd even be the one to do it. Before I knew it, I was doing it and now its over.


All the way up to the date of our inaugural year I was feeling unprepared, afraid I was forgetting terribly important things, or simply that the event would be uneventful. I could not have been more unprepared for the sheer success of PyCarolinas, from the presentations everyone was able to enjoy to the success of the food and drinks we provided to keep them all going to the amazing sense of community and connectedness everyone at the conference obviously felt.

How Did I Get Myself Into This

This was not only the first conference I ran, but the first involvement in running an event beyond a dozen-person hacknight for TriZPUG, so "out of my comfort zone" accurately describes how I felt during the months leading up to October 20th and 21st.
I had mentioned a few times, in a few places, that the carolinas (and the south east in general) need a Python conference. What I meant was "Hey, someone else should run a Python conference, so I can attend."
But, no one did.
The catalyst was Chris Calloway finding the great space we used, and pushing to reserve it for the event. Once he had those wheels moving, it was up to me to make something happen at the time and place we now found ourselves with.

Pulling it Off

I did the best I could with no idea what I was doing.
We did a lot of things right on our first year, which is great.
  • There was coffee to spare. It was good coffee
  • There were pastries and muffins all day long
  • The schedule and talk selection was well varied and interesting
  • Food trucks were picked to keep lunch costs down (catering is expensive)
  • We had amazing shirts designed by Julia Elman of Caktus Group, one of our sponsors
The call for proposals was out pretty early, which I think was good. Lots of our speakers were able to practice their talks to polish, and this really showed.
I could not have done this alone, and I need to thank everyone who made PyCarolinas 2012 possible.
Chris Calloway was invaluable.
He kicked off everything with a space to actually have this event. Chris spent countless hours negotiating with the UNC departments responsible for our needs between the space of the conference and the parking lot we reserved for our lunch trucks. Chris has long been the heart of our local user group, TriZPUG, and he carried that enthusiasm and commitment to his help in making PyCarolinas a reality.
Thank you, Chris.
Kurt Grandis was tireless.
The great lunches we had from the Only Burger truck were possible because of all the leg work Kurt did hunting down great options. The crowd was really happy about the food truck, and everyone should thank Kurt for the great good.
Thank you, Kurt.
Rebecca Lovewell was generous.
She organized our well received coffee reserves, which never ran out, and helped underwriting our never ending pastries. Every conference I've been to seems plagued with ran-out-of-coffee syndrome, so we should all thank her for helping us all stay awake through the exhausting weekend.
Thank you, Rebecca.
Andrew Thompson was a life saver.
I made the grave mistake of failing to organize volunteers well, or at all, during the actual conference. I also underestimated the quick pace and difficulty of keeping up with registration in the first morning! But, Andrew stepped in (we had never met before) and helped run the registration table, doing a much better job of it than I was. Without his spontaneous volunteering, I would have been unable to leave registration and take care of everything else that needed attending that morning.
Thank you, Andrew.
Of course, our sponsors made everything possible.
Thank you, Caktus Group.
Thank you, Google.
Thank you, 10 Gen.
Thank you, Marakana.
Thank you, Cox Media.
Thank you, Wingware.
Thank you, Kitware.
Thank you, Meta Metrics.
Thank you, RochApps.
Thank you, Heroku.
Thank you, Red Hat.
And, a special thanks to Joe Copp and Andrew Kuchling, who both made personal donations in support of our fledgeling event.
And, without our amazing speakers to fill our schedule and share their knowledge and experiences with us, there would be no conference to attend in the first place.
Thank you, to our keynote speakers Lynn Root and Gary Bishop.
Thank you to all of all session speakers Randall Hunt, Joseph S. Tate, A.M Kuchling, Chris Church, Paul J Kowalczyk, PhD, Rick Copeland, Mark Lavin, Michael Manfre, David Ray, Vinod Kurup, Wayne Witzel III, William Sams, Al Snow, Barry Peddycord III, Kenneth Reitz, Matthew Frazier, Julia Elman, Fred Alger, Jeff Heard, Brian Painter, Tim Hopper, Simeon Franklin, Francois Dion, Flaviu Simihaian, Chris Calloway, Michael DeHaan, Dr. Brian J. Soher, Philip Semanchuk, and Brad Crittenden.
But, what would a conference be without an audience?
I want to give a very sincere thank you to everyone who attended this first year. You all came to an event that had never happened before, so you had no idea what to expect. This faith in our new occurance is not missed, and I hope we have lived up to whatever it was you hoped to get out of the weekend. I hope that PyCarolinas was good enough use of your time that I will not only see each and every face again next year, but that you'll all spend the year pumping up your local user groups and Python community and bring more people along next year.

Next Year

There will be a next year. It will be smoother.
While the first PyCarolinas was amazing, it is important to remember what could be done better. I've kept a "to done" list. A list of things I should have done, or done different.
  • Seek out volunteers for the registration desk ahead of time
  • Seek out session chair volunteers
  • Seek out volunteers to clean-up afterwards
  • Print out better programs with sponsor logos. They deserved more thanks.
  • Prepare the badges and sign-in sheet better. I forgot to alphabetize.
  • The badges should show last names better
  • and, they should have shown the conference name and logo!
and, finally
Even though I talked to the people responsible for the space we used about scheduling the cameras to record I should have confirmed this within the week before the conference, in case there was a mixup. Which, I am very sorry to report, there was. We do not have the recordings of all our wonderful talks, as had been expected. I am terribly sorry for this.
Not the least of reasons being that I didn't actually see any talks in full the entire weekend, personally.
If anyone has any other suggestions, please let me know what could have been better!
Thank you to everyone who attended. Thank you again to all our sponsors and speakers. I hope to see everyone there again next year!

-- Calvin Spealman

Comments

kcunning said…
I would love to attend next year :) This year, it didn't quite line up for me, but I'll make room in 2013!

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on

The Range of Content on Planet Python

I've gotten a number of requests lately to contribute only Python related material to the Planet Python feeds and to be honest these requests have both surprised and insulted me, but they've continued. I am pretty sure they've come from a very small number of people, but they have become consistent. This is probably because of my current habit of writing about NaNoWriMo every day and those who aren't interested not looking forward to having the rest of the month reading about my novel. Planet Python will be getting a feed of only relevant posts in the future, but I'm going to be honest: I am kind of upset about it. I don't care if anyone thinks it is unreasonable of me to be upset about it, because the truth is Planet Python means something to me. It was probably the first thing I did that I considered "being part of the community" when I submitted my meager RSS feed to be added some seven years ago. My blog and my name on the list of authors at Plan

Pythonic Defined

Introduction Losing is Good Strings Dictionaries Conclusion Introduction Veterans and novices alike of Python will hear the term "pythonic" thrown around, and even a number of the veterans don't know what it means. There are times I do not know what it means, but that doesn't mean I can define a pretty good idea of what "pythonic" really means. Now, it has been defined at times as being whatever the BDFL decides, but we'll pull that out of the picture. I want to talk about what the word means for us today, and how it applied to what we do in the real world. Languages have their strengths and their idioms (ways of doing things), and when you exploit those you embrace the heart of that language. You can often tell when a programmer writing in one language is actually more comfortable with another, because the code they right is telltale of the other language. Java developers are notorious for writing Java in every language they get their hands on. Ho