Since being back in "the real world" - things have been crazy. I'm working on a PEP (albeit slowly) and trying to ramp up on python core-development while simultaneously trying to work on the safetheading stuff and several PyMag articles. Did I mention that I can't work on any of this during the day? *head explodes*
Oh, and there was Easter Dinner to attend to as well? I do so love cooking.
I envy the Googler's out there and the others who get an allotment of time to "contribute to open source" or explore other technical avenues for many reasons, the obvious of which is "having more time to do something else".
To boot, I've been compulsively saving things to read/catch up on in my newreader. I'm up to about 205 items to cycle through.
All the whining done - I never did get to "close out" PyCon.
The last two years I've gone, I never stayed long enough on Sunday to see or do anything useful. This year, I wanted to stay through the core sprint, but alas - I had to go back Monday.
I was at least able to finish out the con, see some great talks and do a lightning talk on concurrency stuff. I also got to sit through Brett's intro to core development (which was great by the way) and try to get up and hacking on core.
I unfortunately spaced out during most of the morning keynotes (except for the OLPC update) as the mozilla-world isn't my particular cup of Joe. In addition to that, I got tapped by Jacob Kaplan-Moss to do a lightning talk (they had an open slot) - I said yes, and promptly went heads-down to grind out and condense as much information as I could as fast as I could.
I hit up "more iterators in action" - it was a great talk, and I am looking forward going back over the material. It was "information rich". After that was one of my favorite talks of the conference: Core Python Containers by Raymond D Hettinger - that talk was fantastic. I need to re-watch the video when it goes on "the youtube" to really absorb the content again, but it was really a great talk.
Then I hopped into the 2to3 talk - but then skipped out as I've been over that one before, and slipped into the OLPC testing talk by Titus (yes, I was the guy who cheered when he showed his kid on the screen). Titus is probably one of the best presenters PyCon has. He's engaging, funny and knows his stuff cold. Some of the tools he showed in the OLPC talk are really interesting for test automation, even if UI stuff is not my cup of tea, the back end stuff he's done with peekaboo is awesome.
Also, Titus' post on the "Death Spiral" is a must read. I liked my analogy (in the comments) that all Good Chefs (and cooks!) taste their food as they prepare and cook it to ensure it well, tastes good. The same applies to testing.
After that - it was fear. Yes, I was scared out of my mind to stand up the few hundred people left at the conference and do my lightning talk. According to people I trust, it was well received - and I got information out, which is great.
After that is was sprint-time, and a good time indeed.
PyCon this year was great, even if it did have it's "warts" with the sponsor stuff - it was also huge. I can't wait for next year. And thanks to everyone who asked about the kiddo and house. Right now, things are going well (albeit expensively with the house).
Onto the Miscellanea:
I stumbled onto this blog in the last few days, namely - this post. The author has made a few interesting posts on the (for lack of a better term) "pro static language" argument, here, here and here. It's an interesting read, even if I disagree with some of what the author says. Both static and dynamic (read: Duck/Runtime) typed languages have their pros and cons.
Speaking of Types, I found this article "What to know before debating type systems" quite good.
@foo @bar(...) @baz @what @yourekiddingmeright def func(): insert lollerskates
Which made me realize, even among consenting adults, there's some people who drink way too much and code.
Which brings us to my final tidbit: Concurrency. There was some hubbub around the new Fork/Join stuff coming to the Java 7 JRE, the stuff outlining what's coming (including the original paper) is a series of "good reads".
I'd like to carve some time (yeah. ok.) out to think about a concurrency library similar in nature to java.util.concurrent for Python. I think it would be a useful addition, especially with the hopeful prospect of safethreading coming to town.
Back to my articles and other associated work.