[OKC JUG] Dojo sometime soon?

Jeff Bowman jeff at bowmansarrow.us
Fri Jun 12 07:27:51 PDT 2009


Well,my email client added that T. I guess I should proof read my email better!

I do have both a mac (ihackintosh) and skype but primarily run linux (and skype). 

Instead of Dolphin, how about Pharo (forked version of Squeak) which is more cross platform?

For Lisp, check out http://gigamonkeys.com/book which you can read online as well as get a Lisp preconfigured dev environment to play in.

Jeff

"Brett L. Schuchert" <schuchert at yahoo.com> wrote:

>Dude,
>
>It's Smalltalk, not SmallTalk - for reals.
>
>As for remote, you have a mac? It's easy to remote desktop in. Then  
>all we'd need is skype and a way to amplify what you're saying. So I'm  
>game, can to CoCo pull it off?
>
>As for the languages, I like (but don't really know) Lisp. I know  
>Smalltalk and love it but I'm very rusty. However, I have some stuff a  
>friend of mine did that gives decent refactoring and TDD in Dolphin  
>Smalltalk. Haskell, no experience. I've read some code. Scala, written  
>some code, somewhat game.
>
>As you're not going to be on site initially, I'd say that rules out  
>Lisp unless someone wants to take that on.
>
>Brett
>On Jun 12, 2009, at 12:01 AM 6/12/09, Jeff Bowman wrote:
>
>> I'm interested also, but I'm currently on deployment to Austin. Is  
>> remote participation accepted?
>> How would that work?
>>
>> Here is my language list: (the top two I can contribute some  
>> (significant) experience in,
>> the bottom two I'm still learning, and would be interested in other  
>> peoples experience and solutions)
>>
>> Lisp
>> SmallTalk
>> Haskell
>> Scala
>>
>> Jeff
>>
>> On Jun 11, 2009, at 3:19 PM, Brett L. Schuchert wrote:
>>
>>> 3 minutes is too short, I agree. I think 10 minutes is too long.
>>>
>>> I've been reading and it seems that 7 minutes is a good upper limit  
>>> (by the way, I'm thinking of the randori style). We can mitigate  
>>> that by starting with one time limit and then when/if the nature of  
>>> the work changes, we can change the time limit (I have a particular  
>>> problem in mind).
>>>
>>> Initially, I'd recommend something like 5 minutes and change to  
>>> switch groups. I've already got a solution for this on my machine.
>>>
>>> RE: FitNesse
>>> 	We can easily hit Java, .Net and less easily C/C++
>>> 	There are also Ruby bindings as well, so that's a pretty good start.
>>> 	Also, any JVM-based languages will work
>>>
>>> RE: Languages
>>> 	Totally agree. I'd be there for just about any language
>>>
>>> I have several problems we can do right now and I'm happy to send  
>>> them out. How about this:
>>> 	Location:		CoCo
>>> 	Time:		5:30 - 9
>>> 	Day:			Tuesday
>>> 	Language:	<what language will get best participation?> Java/C#/ 
>>> Ruby/C++
>>>
>>> If this is cool, I'll send out several problems people can try out  
>>> and we'll pick one for Tuesday evening between 5:30 and 6:00
>>>
>>> Brett
>>> On Jun 11, 2009, at 8:14 AM 6/11/09, Chad Gorshing wrote:
>>>
>>>> I personally would like to support the CoCo as much as we can, so  
>>>> I my
>>>> vote is to have this at the CoCo.  Mark is very busy the next couple
>>>> of weeks, so I'm not sure if we could get a response from him for a
>>>> while (Ken and/or Michael is better at reaching him than I am).
>>>>
>>>> I do not see a problem with the time, but I would also rule out
>>>> Wednesday nights.  So basically leaving Mon, Tues, and Thurs  
>>>> (assuming
>>>> people do not want this eating up into their weekend).  Derrick  
>>>> might
>>>> be able to provide more information on the days being available.
>>>>
>>>> I'm all on board for the choices of languages, but this shouldn't  
>>>> be a
>>>> limiting factor, but merely a suggestion.  I would love to see what
>>>> other people are capable of, and introduce me to things such as
>>>> Haskell, Scala ...etc.
>>>>
>>>> At least for getting this thing off the ground, I would rather be
>>>> given the problem so people could work on it a bit and start to get
>>>> into the groove.  As we 'mature' this along, then we could do more
>>>> problems fresh at the meeting.  I guess another option would be to
>>>> give out a problem in advanced but to also have somebody bring a
>>>> problem and have people solve it fresh.  I am heavily for TDD and I
>>>> would love to see how people used TDD practices while doing some of
>>>> the Euler problems (I've had a hard time grasping how to implement
>>>> these practices while doing some of Euler's problems).  I would  
>>>> *love*
>>>> to see how are using BDD, I have tried this privately while writing
>>>> some python code using pyspec.
>>>>
>>>> If the problems get a little more involved we could also get a
>>>> FitNesse wiki set up for an acceptance testing framework (but the
>>>> languages are limited) ... but this is quite possibly waaaay down  
>>>> the
>>>> road.
>>>>
>>>> How does everybody feel about three minute pair switching?  I do not
>>>> think this is enough time, I was thinking 10 as a minimum.  I'm  
>>>> asking
>>>> for experience and/or input here.
>>>>
>>>> Any way we decide to go is fine with me, getting this thing off the
>>>> ground is what the most important aspect is.  We just need to pull  
>>>> the
>>>> trigger and go.  So I'll roll with whatever and retrospect while  
>>>> this
>>>> baby starts to grow (hopefully).
>>>>
>>>> I'm glad to see people interested in this and I'm looking forward to
>>>> be put in my place :)
>>>>
>>>> Chad
>>>>
>>>> On Thu, Jun 11, 2009 at 12:40 AM, Brett L. Schuchert<schuchert at yahoo.com 
>>>> > wrote:
>>>>> Derrick, et. al.,
>>>>>
>>>>> I'd be happy to start something. I would love a regular, multi- 
>>>>> language
>>>>> dojo.
>>>>>
>>>>> I see three options for location:
>>>>>     Valtech - they have offered their space before (Kenyatta? Mark
>>>>> Smith?)
>>>>>     CoCo - this is separate from the OkC JUG as far as I can see,  
>>>>> so $$
>>>>> for the space?
>>>>>     Public Libraries - depends on # people, but this has been a  
>>>>> good
>>>>> option in the past
>>>>>
>>>>> I'd say some evening, from 5:30 PM to 9:00, people can come and  
>>>>> go as they
>>>>> see fit.
>>>>>
>>>>> I propose next week. Are any nights out of the question other  
>>>>> than Friday?
>>>>>
>>>>> Initial languages:
>>>>>     Java
>>>>>     C#
>>>>>     Ruby
>>>>>     C++
>>>>>     Java Script
>>>>>
>>>>> (I suggest we work on the same problem across the languages.)
>>>>>
>>>>> Any takers on that? I can propose a problem (or a few).
>>>>>
>>>>> We can:
>>>>>     Start from scratch
>>>>>     Begin somewhere "in the middle"
>>>>>     Use TDD (my preference)
>>>>>     Use BDD (or this would be cool as well)
>>>>>     Or not (I'm willing but much less interested)
>>>>>
>>>>> Here is one proposal from the above:
>>>>>     Monday, 5:30 - 9:00
>>>>>             5:30 - 6:00 meet and greet, set ground rules
>>>>>             6:00 - 8:30 dojo, one pair working, all else  
>>>>> observing and
>>>>> commenting, pairs changing every 3 minutes
>>>>>             8:30 - 9:00 fish bowl
>>>>>     Location: Downtown Public Library
>>>>>     Java
>>>>>     Starting from scratch on a problem I'll bring
>>>>>             It will involve basic TDD as well as design patterns
>>>>>     Using TDD
>>>>>
>>>>> Brett
>>>>> On Jun 10, 2009, at 5:00 PM 6/10/09, derrick parkhurst wrote:
>>>>>
>>>>>> On Wed, Jun 10, 2009 at 4:45 PM, Brett L. Schuchert<schuchert at yahoo.com 
>>>>>> >
>>>>>> wrote:
>>>>>>>
>>>>>>> After this week's presentation I'm Jonesin' for a code dojo.  
>>>>>>> Anybody
>>>>>>> interested?
>>>>>>>
>>>>>>> We'd need a location and an overhead projector but I'd be happy  
>>>>>>> to bring
>>>>>>> a
>>>>>>> problem and a computer we could work on.
>>>>>>>
>>>>>>> Brett
>>>>>>
>>>>>> I am. In fact, I encouraged Chad to start a dōjō out of the  
>>>>>> okcCoCo -
>>>>>> The CoCo Dōjō?. I could easily see community members taking on  
>>>>>> the
>>>>>> role of sensei for various programming languages. Let me know  
>>>>>> how I
>>>>>> can help get this started.
>>>>>>
>>>>>> Cheers,
>>>>>> Derrick
>>>>>>
>>>>>> --
>>>>>> Derrick Parkhurst, Ph.D.
>>>>>> Thirty Sixth Span Internet Technologies
>>>>>> http://thirtysixthspan.com
>>>>>>
>>>>>> --------------------------------------------------------------------------------
>>>>>> okcCoCo: http://okcCoCo.com
>>>>>> OpenBeta: http://openbeta.extendedbeta.com
>>>>>> LinkedIn: http://www.linkedin.com/in/derrickparkhurst
>>>>>> Twitter: http://www.twitter.com/ThirtySixthSpan
>>>>>> _______________________________________________
>>>>>> Jug mailing list
>>>>>> Jug at lists.okcjug.org
>>>>>> http://lists.okcjug.org/listinfo.cgi/jug-okcjug.org
>>>>>
>>>>> _______________________________________________
>>>>> Jug mailing list
>>>>> Jug at lists.okcjug.org
>>>>> http://lists.okcjug.org/listinfo.cgi/jug-okcjug.org
>>>>>
>>>> _______________________________________________
>>>> Jug mailing list
>>>> Jug at lists.okcjug.org
>>>> http://lists.okcjug.org/listinfo.cgi/jug-okcjug.org
>>> _______________________________________________
>>> Jug mailing list
>>> Jug at lists.okcjug.org
>>> http://lists.okcjug.org/listinfo.cgi/jug-okcjug.org
>>
>> Amateurs work until they get it right...
>> ... Professionals work until they can't get it wrong.
>>
>>
>>
>> _______________________________________________
>> Jug mailing list
>> Jug at lists.okcjug.org
>> http://lists.okcjug.org/listinfo.cgi/jug-okcjug.org
>_______________________________________________
>Jug mailing list
>Jug at lists.okcjug.org
>http://lists.okcjug.org/listinfo.cgi/jug-okcjug.org


More information about the Jug mailing list