[KyOSS Discuss] Idea for a meeting format - Code retreat

alan blount alan at zeroasterisk.com
Tue May 28 16:09:55 EDT 2013


Looked at it, but haven't implemented myself.  I've played with code which
has.

>From what I see it's basically testing from the "use case" or "end result"
of some code, vs testing the atomic functions within it.


On Tue, May 28, 2013 at 2:49 PM, Deven Phillips <deven.phillips at gmail.com>wrote:

> Have any of you started looking at "behavior driven development"? I'm
> thinking about putting together a presentation for a future JUGGL meeting
> about it.
>
> Deven
> On May 28, 2013 2:25 PM, "alan blount" <alan at zeroasterisk.com> wrote:
>
>> I agree, I'm fairly new to TDD (though I've done unit tests for a while)
>> but I'm a big fan...  that said, I still don't do it all the time, old
>> habits and all...
>>
>>
>> On Tue, May 28, 2013 at 1:56 PM, Eric Lathrop <eric at ericlathrop.com>wrote:
>>
>>> I'd be happy to do another code retreat, but it would probably be too
>>> long for a KYOSS meeting.
>>>
>>> I'm also happy to talk about TDD to anyone who will listen. I really
>>> felt like I got the best understanding of TDD from doing it, so I like the
>>> hands-on workshop approach.
>>>
>>> John Hicks <johnhicks at gulfbridge.net> wrote:
>>>>
>>>> Eric Lathrop led a "Code Retreat" last December that did something like
>>>> what you describe, Barton. We paired up, were all given the same task to
>>>> code, each pair coded it with the language of our choice, and then we all
>>>> compared our solutions. After that we changed partners and repeated the
>>>> process with a new task (building on the last task). Etc. This was my first
>>>> introduction to test-driven development. It definitely got me out of my
>>>> comfort zone (which is what us old codgers need to be doing) and got the
>>>> (coding) juices flowing.
>>>>
>>>> For a better description (including video), see:
>>>> http://kyoss.org/Event/1739
>>>>
>>>> John
>>>>
>>>> On 05/28/2013 01:20 PM, Barton Chittenden wrote:
>>>>
>>>>  I'm not against that, but I was thinking something more along the
>>>> lines of
>>>>
>>>>  Using the open source tools of your choice, automate the following
>>>> process:
>>>>
>>>>    1. Edit a text file, create a program which prints the result of
>>>>    2+3 to standard out
>>>>    2. Check the program for correctness
>>>>    3. Run the program
>>>>    4. Check that it correctly emitted '5'. Print "OK" if the program
>>>>    is correct, "Not OK" if the program doesn't print "5".
>>>>
>>>> There are a bajilion different ways to approach this. What I'm most
>>>> interested in is the actual process of talking through this with someone
>>>> else, and the variety of solutions that could be used.
>>>>
>>>>
>>>> On Tue, May 28, 2013 at 1:01 PM, Deven Phillips <
>>>> deven.phillips at gmail.com> wrote:
>>>>
>>>>> Perhaps a session where we all share our favorite command-line-fu?
>>>>>  On May 28, 2013 12:24 PM, "Barton Chittenden" <bartonski at gmail.com>
>>>>> wrote:
>>>>>
>>>>>>  I happened to look at an event held by the VimCLE meetup (Cleveland
>>>>>> VIM user group). They did something that they called Vimswap:
>>>>>>
>>>>>>
>>>>>> Bring your laptops: This month, I'd like to try an experiment to get
>>>>>> the knowledge transfer going. We'll break up and spend 20 minutes pairing
>>>>>> on a real-world-eque editing task, five minutes hearing from the pairs on
>>>>>> what was learned, five minute break, and repeat. Please comment on meetup
>>>>>> if you'd like to suggest editing tasks, otherwise we'll choose VimGolf
>>>>>> tasks.
>>>>>>
>>>>>>  http://www.meetup.com/VimCLE/events/47804852/
>>>>>>
>>>>>>  I think that this would be a really interesting way to mix things
>>>>>> up at KYOSS. I don't know exactly which topic that we would use... to a
>>>>>> certain extent, that's a challenge with KYOSS... we might consider trying
>>>>>> two or three tasks rather than one, just so that we have enough diversity
>>>>>> to cover everyone's interests and current abilities.
>>>>>>
>>>>>>  Anyway, I'm just throwing this out there for comment.
>>>>>>
>>>>>>  --Barton
>>>>>>
>>>>>>  _______________________________________________
>>>>>> KyOSS-Discuss mailing list
>>>>>> KyOSS-Discuss at kyoss.org
>>>>>> Subscribe by sending email to kyoss-discuss-subscribe at kyoss.org
>>>>>> Unsubscribe by sending email (from the address you wish to
>>>>>> unsubscribe) to kyoss-discuss-unsubscribe at kyoss.org
>>>>>> Difficulty unsubscribing? Check your email headers for originally-to
>>>>>> address in case you are forwarding your mail.
>>>>>> More options at
>>>>>> http://kyoss.org/cgi-bin/mailman/listinfo/kyoss-discuss
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> KyOSS-Discuss mailing list
>>>>> KyOSS-Discuss at kyoss.org
>>>>> Subscribe by sending email to kyoss-discuss-subscribe at kyoss.org
>>>>> Unsubscribe by sending email (from the address you wish to
>>>>> unsubscribe) to kyoss-discuss-unsubscribe at kyoss.org
>>>>> Difficulty unsubscribing? Check your email headers for originally-to
>>>>> address in case you are forwarding your mail.
>>>>> More options at
>>>>> http://kyoss.org/cgi-bin/mailman/listinfo/kyoss-discuss
>>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> KyOSS-Discuss mailing listKyOSS-Discuss at kyoss.org
>>>> Subscribe by sending email to kyoss-discuss-subscribe at kyoss.org
>>>> Unsubscribe by sending email (from the address you wish to unsubscribe) to kyoss-discuss-unsubscribe at kyoss.org
>>>> Difficulty unsubscribing? Check your email headers for originally-to address in case you are forwarding your mail.
>>>> More options at http://kyoss.org/cgi-bin/mailman/listinfo/kyoss-discuss
>>>>
>>>>
>>>> ------------------------------
>>>>
>>>> KyOSS-Discuss mailing list
>>>> KyOSS-Discuss at kyoss.org
>>>>
>>>>
>>>>
>>>>
>>>> Subscribe by sending email to kyoss-discuss-subscribe at kyoss.org
>>>> Unsubscribe by sending email (from the address you wish to unsubscribe) to kyoss-discuss-unsubscribe at kyoss.org
>>>>
>>>>
>>>>
>>>>
>>>> Difficulty unsubscribing? Check your email headers for originally-to address in case you are forwarding your mail.
>>>> More options at http://kyoss.org/cgi-bin/mailman/listinfo/kyoss-discuss
>>>>
>>>>
>>> _______________________________________________
>>> KyOSS-Discuss mailing list
>>> KyOSS-Discuss at kyoss.org
>>> Subscribe by sending email to kyoss-discuss-subscribe at kyoss.org
>>> Unsubscribe by sending email (from the address you wish to unsubscribe)
>>> to kyoss-discuss-unsubscribe at kyoss.org
>>> Difficulty unsubscribing? Check your email headers for originally-to
>>> address in case you are forwarding your mail.
>>> More options at http://kyoss.org/cgi-bin/mailman/listinfo/kyoss-discuss
>>>
>>
>>
>> _______________________________________________
>> KyOSS-Discuss mailing list
>> KyOSS-Discuss at kyoss.org
>> Subscribe by sending email to kyoss-discuss-subscribe at kyoss.org
>> Unsubscribe by sending email (from the address you wish to unsubscribe)
>> to kyoss-discuss-unsubscribe at kyoss.org
>> Difficulty unsubscribing? Check your email headers for originally-to
>> address in case you are forwarding your mail.
>> More options at http://kyoss.org/cgi-bin/mailman/listinfo/kyoss-discuss
>>
>
> _______________________________________________
> KyOSS-Discuss mailing list
> KyOSS-Discuss at kyoss.org
> Subscribe by sending email to kyoss-discuss-subscribe at kyoss.org
> Unsubscribe by sending email (from the address you wish to unsubscribe) to
> kyoss-discuss-unsubscribe at kyoss.org
> Difficulty unsubscribing? Check your email headers for originally-to
> address in case you are forwarding your mail.
> More options at http://kyoss.org/cgi-bin/mailman/listinfo/kyoss-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://kyoss.org/pipermail/kyoss-discuss/attachments/20130528/ca7cb66e/attachment-0001.html>


More information about the KyOSS-Discuss mailing list