Tuesday, December 11, 2012

Python Lightning talks ideas

PYPTUG meeting

We are starting our preparation early for our January PYPTUG meeting. It will be in Kernersville again, if we can get the same conference room.

We already have our main speaker set up, but we really want to ramp up participation through lightning talks.

We are also looking for talks for February and subsequent months. These can be 30 or 45 minutes talks. If you are not a PYPTUG member, but you would like to give a talk and you don't mind driving to the Piedmont Triad, contact us ( twitter @pyptug or email us at pyptug _at_ gmail.com ) and we'll try to schedule something.

Lightning talks

A lightning talk can be up to 5 minutes or up to 10 minutes on
something you have learned about Python, a module, your favorite
editor or a project they did with Python.

Some ideas

Just a few suggestions for lightning talks, might stir something in those little grey cells of yours...

-how python replaced matlab at your university
-the ins and outs of the requests module
-paramiko vs sh
-how pythonic are you?
-how easy is easygui?
-dtrace enabled python
-how to program FPGAs with Python
-Python(x,y) saved my life
-all you ever wanted to know about generators
-the details of the _____ algorithm
-how to use mercurial
-my vim-fu is strong
-pep8, pylint and PyFlakes walk into a bar...
-the property keyword
-multilingual support in a python application
-why do you like python
-why do you not like python
-20 modules you cant do without
-python book review
-python blog review
-@decorators are bliss
-@decorators are evil
-ironpython
-pygames for everyone
-the python foundation
-python for iOS
-python for android
-swig
-doctest
-docopt
-nose
-pypi
-pypy
-pipy (just playing, it has nothing to do with python)

But, at the end of the day, you know more than I do what you are excited about. So go ahead, don't be shy and volunteer for a lightning talk!

3 comments:

  1. Would love to speak about more than half of the topics, but unfortunately, I live far away. :(

    ReplyDelete
  2. This comment has been removed by a blog administrator.

    ReplyDelete
  3. This comment has been removed by the author.

    ReplyDelete