Skip to main content

PyCon 2013 Posts I want to see

PyCon 2013 will be my third PyCon, and I'm walking into it with a better idea what I'm hoping for than my first two. Here is my shortlist for talk hopes.

  • Python inside Government
    Are any federal, state, or local governments using Python internally? In any important or large ways? Maybe at the national archives or the library of congress? I want to know about these things! Does the IRS crunch my taxes with Python?

  • Python and Big Data
    Working with large datasets fascinates me, probably because I don't get the opportunity to do so. I'd love to see where Python is being used to crunch big datasets. I wonder if gets used in any pipelines in processing results from CERN? Or maybe diagnosing medical tests?
  • Python close to the wire, embedded or working with wire protocols
    Using Python in mobile devices, embedded devices, or implementing binary protocols on the wire that need to work fast and with low latency? These are things people often don't think Python does well, so prove them wrong.
  • Python in movies
    Pixar, Disney, I know you guys are out there! Is python used in stages of the pipeline to make all those 3D movies I take my kids to see?
  • Community-centric talks, please!
    These are personally interesting to me, because I want to build community. I want to learn from more people who are great at it.
If you can give any of these talks, or any talk at all, submit your proposal for PyCon 2013!

Comments

pyDanny said…
Unfortunately, you won't see Disney or Pixar developers speaking at conferences. Because of creative controls Disney puts on it's staff so they don't blow open the plots of movies that pay for a thousand people at a time, they heavily restrict their speaking engagements.

This also might be the case for Dreamworks and various American effect companies, but I'm not certain. From my experiences at PyCon New Zealand, I do believe WETA digital gives it's developers a lot of freedom.

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 only re…

Interrupting Coders Isn’t So Bad

Here’s a hot take: disrupting coders isn’t all that bad.

Some disruptions are certainly bad but they usually aren’t. The coder community has overblown the impact. A disruption can be a good thing. How harmful disruption might be a symptom of other problems.

There are different kinds of disruptions. They are caused by other coders on your team, managers and other non-coders, or meetings throughout the day.

The easiest example to debunk is a question from a fellow developer. Imagine someone walks over to your desk or they ping you on Slack, because they have “one quick question.” Do you get annoyed at the interruption when you were in the middle of something important? You help out your teammate quickly and get back to work, trying to pick up where you left off. That’s a kind of interruption we complain about frequently, but I’m not convinced this is all that bad.

You are being disrupted but your team, of which you are only one member of the whole unit, is working smoothly. You unstuck …

How To Care If BSD, MIT, or GPL Licenses Are Used

The two recent posts about some individuals' choice of GPL versus others' preference for BSD and MIT style licensing has caused a lot of debate and response. I've seen everything as an interesting combination of very important topics being taken far too seriously and far too personally. All involved need to take a few steps back.

For the uninitiated and as a clarifier for the initiated, we're dealing with (basically) three categories of licensing when someone releases software (and/or its code):
Closed Source. Easiest to explain, because you just get nothing.GPL. If you get the software, you get the source code, you get to change it, and anything you combine it with must be under the same terms.MIT and BSD. If you get the software, you might get the source code, you get to change it, and you have no obligations about anything else you combine it with.The situation gets stickier when we look at those combinations and the transitions between them.

Use GPL code with Closed S…