addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwchatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrosseditemptyheartexportfacebookfolderfullheartglobegmailgoogleimageimagesinstagramlinklocation-pinmagnifying-glassmailminusmoremuplabelShape 3 + Rectangle 1outlookpersonplusprice-ribbonImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruseryahoo

Python Atlanta is this Thursday!

From: Brandon R.
Sent on: Monday, September 7, 2009 2:20 PM
Python Atlanta folks,

Our regular September meeting is this Thursday evening!  Alfredo Deza
will give a short talk on "Continuous Integration", in which tests run
continuously while you develop, and I myself will give a talk on
"Template Languages" and how they can be useful to both systems
administrators and web site authors.

The meeting details are here:

   http://www.meetup...­

Does anyone else have talks to present or suggest?  Let me know.

Lastly, I would like your input on a new idea for our group!  What if we
had a monthly feature where someone offered to let us look at a piece of
Python code they'd written, and we looked at it together to figure out
how it could best be cleaned up and tested?  There could be several
benefits:

 * The group could learn new things by looking at the code and seeing
   what it was doing, and thus learning from its author.

 * The author could then learn from the group, as we responded with lots
   of hints, tips, and tricks about improvements and clarifications that
   could be made to the code.  This would very often lead to interesting
   discussion amongst group members about the trade-offs between
   efficiency, clarity, maintainability, and extensibility.

 * I could, optionally, summarize our ideas about the code in a blog
   post to share our results with the Python community and generate
   interest in our Atlanta group.

There are several ways this could work:

 1. The code could be presented, at a meeting, by the author themselves,
    and everyone could weigh in with ideas.

 2. Or, instead, the code could be submitted to me for presentation
    "anonymously" so that it would not be publicly revealed who wrote
    the code, in case someone wanted to ask about a script but not
    reveal at which company it was being used.

 3. It could happen at a meeting, where we all talk about it.

 4. Or, it could happen as a discussion on the mailing list.

 5. We could almost do it as a contest, where the code is sent out a day
    or two before the meeting, and then everyone brings their ideas
    about it to the meeting.

What does everyone think?  My vote is that we reveal the code a day or
two before the meeting, then we all discuss it there, then I write up
the results for the PyAtl blog.  Does anyone have any code they would
like to share - a script that you think could be faster or better, but
that you lack the expertise to easily improve?  Let me know.

And, I look forward to seeing you guys on Thursday!

-- 
Brandon Craig Rhodes   [address removed]   http://rhodesmill...­

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy