Liveblogging Pycon (Day 4)

by jesse in ,

Ahh, Day 4. The day I get to crawl through the airports back to Boston. It's going to be a short day (we have to leave @ noon for our flight) but I'll catch the keynote and at least the second revised run of the Agile testing presentation. I had a bit of a Good Thought last night, and once I get back to Boston, I am going to check with my Robot Masters to see if I can start community work on something instead of making it a Product thing. Since I already have Secret Project A-X, I will call this "Secret Project Squirrel Swarm" (a hint is in the name).

I've been sitting in the Bram Cohen keynote for awhile now. The interview has had a few interesting points, but for the most part, it's non technical, and not very compelling. I would have liked to have hear more of his thoughts about Python, implementations, etc.

Largely, the interview style just simply did not work. Of course, listening to the tangents and the discussion on how to scam credit card debit was interesting. (ok maybe not)

I think more compelling keynotes (in the thread of Guido's would be good for next year).

I'm going to sit in on the Agile testing followup now.

Well, I'm actually sitting at the airport. I ended up leaving midway through the Agile presentation. I'm already very clear about the subject matter, and again, another presentation on the testing of web applications.

I know the tools involved, BuildBot,, etc. Largely, none of these tools (outside of Selenium and maybe Twill) are remotely useful in my work. There's a reason we write our own testing framework.

Kudos to the guys for presenting the subject matter. I'm irritated I missed the full session, but I have the slides. Again, I'm looking at this through the narrow view of "how does this apply to me". And none of the Agile stuff presented really did (or it's old hat for me).

So, now I am sitting in DFW grinding through my post con thoughts - I've already posted my initial critique (and filled AMKs ears with some before I left), but I think instead of being a passive critic, I am going to try to help to make next year better.

I plan on (when I get back and sane again) beginning to outline some presentations I might like to do for next year's Con (provided I get to go). I am also going to give active feedback to the PyCon team, who should be commended and lauded for the job that they did do.

I enjoyed it in a lot of ways, but I can't comment on the ROI for the trip. A 500$ room bill, food, plus 300$ worth of registration fees makes me balk at a trip next year (esp. as it could very well be on my own dime).

Some abstract things I did learn this year:

  • I need to work on getting more of my time fed into the community, I need to examine existing projects, and see if I can find a way of contributing to them, or I need to begin my own
  • The market for experienced Python people *does* exist (of course, I knew that ahead of time - there's a bunch of places in Boston hiring
  • There's a lot of wicked smart people within the community, again - I regularly feel as if I am the janitor in a room filled with rocket scientists.
  • In addition to being smart, there's a lot of nice people there.

I need to do a technical brain dump for work this week, I'll probably post that here too.

(note, I finally got to post this monday)