[socal-piggies] Partial agenda for July meeting

[Daniel Greenfeld]

Hey Grig,

Thanks for being patient with me! Anyway, I've dinged him about it and
will let you know ASAP.

Danny

On Wed, Jul 20, 2011 at 9:27 AM, Grig Gheorghiu
<grig.gheorghiu at gmail.com> wrote:
> Hi Danny -- don't rescind the offer, it would be good to have
> Randall's talk at the meeting (provided we keep it to 20-30 min).
>
> Let me know if he can do it.
>
> Grig
>
> On Tue, Jul 19, 2011 at 11:51 PM, Daniel Greenfeld <pydanny at gmail.com> wrote:
>> Hey all,
>>
>> I just realized this was not what Grig was asking to have at Socal Piggies.
>>
>> This is why I shouldn't send out group emails so far past my bed time. :P
>>
>> Anyway, I guess I'll rescind Randall's talk offer and maybe he can do
>> it next month.
>>
>> Danny
>>
>> On Tue, Jul 19, 2011 at 11:37 PM, Daniel Greenfeld <pydanny at gmail.com> wrote:
>>> Hey Grig,
>>>
>>> I convinced Randall Degges to give a talk on telephony and
>>> django-twilio. It is a good talk cause he also brings up the twilio
>>> and tropo support for Python.
>>>
>>> Danny
>>>
>>> On Mon, Jul 18, 2011 at 9:02 AM, Grig Gheorghiu
>>> <grig.gheorghiu at gmail.com> wrote:
>>>> Anybody else volunteering to show examples of unit tests that saved
>>>> the day for them in terms of finding bugs that would have otherwise
>>>> gone unnoticed?
>>>>
>>>> Grig
>>>>
>>>> On Mon, Jul 11, 2011 at 2:53 PM, Grig Gheorghiu
>>>> <grig.gheorghiu at gmail.com> wrote:
>>>>> We have one 30-minute presentation so far by Evite's very own Dan Mesh:
>>>>>
>>>>> "Python & Go -- Performance, Concurrency, Parallelism"
>>>>>
>>>>> 1. What makes a Python developer look at Google's new programming language
>>>>> 2. A couple of unscientific but fun benchmarks
>>>>> 3. Go style concurrency in Python
>>>>>
>>>>> In the spirit of one of the topics we voted for ("Good testing
>>>>> practices and pointers to new methods/tools") I also propose that
>>>>> people bring examples of at least one unit test that actually found a
>>>>> bug in their code, a bug that would have otherwise remained latent or
>>>>> would have been difficult to discover. We'll have an example from our
>>>>> Evite code to jumpstart this topic.
>>>>>
>>>>> Any suggestions for our #1 voted topic ("Good practice, pitfall
>>>>> avoidance, and module introductions for beginners")?
>>>>>
>>>>> Grig
>>>>>
>>>>
>>>> _______________________________________________
>>>> socal-piggies mailing list
>>>> socal-piggies at lists.idyll.org
>>>> http://lists.idyll.org/listinfo/socal-piggies
>>>>
>>>
>>>
>>>
>>> --
>>> 'Knowledge is Power'
>>> Daniel Greenfeld
>>> http://pydanny.blogspot.com
>>> http://cartwheelweb.com
>>>
>>
>>
>>
>> --
>> 'Knowledge is Power'
>> Daniel Greenfeld
>> http://pydanny.blogspot.com
>> http://cartwheelweb.com
>>
>> _______________________________________________
>> socal-piggies mailing list
>> socal-piggies at lists.idyll.org
>> http://lists.idyll.org/listinfo/socal-piggies
>>
>
> _______________________________________________
> socal-piggies mailing list
> socal-piggies at lists.idyll.org
> http://lists.idyll.org/listinfo/socal-piggies
>



-- 
'Knowledge is Power'
Daniel Greenfeld
http://pydanny.blogspot.com
http://cartwheelweb.com