On Fri, Apr 22, 2011 at 11:54 AM, Le Quoc Thai <[email protected]> wrote: > > > 2011/4/22 Serge Stinckwich <[email protected]> >> >> I just have to remind you that for a Kata, you need to have a problem to >> solve. >> When you start you expose the problem (very simple in usual) and after >> that you start to wrote tests. > > Oh! > So it seems that TDD is a must in any kata, right? Mhmmm... I was thinking > any problem is fine, therefore "Naked Object" (a kind of Domain-Driven > Design) was chosen. > Well, let's take back the idea I had proposed last time: "TDD in Eclipse > with Java" if the aforementioned DDD kata is not suitable.
I'm very interested by "Naked Object" ;-) but i think this is not really a problem for a Kata like the one i propose last time. The description of the problem should be simple enough in order to be done during one session (less than 2 hours). What you could propose is too solve a problem like TennisKate by using the "Naked Object" design by exemple (and TDD) by example. Don't worry, all #codingdojo attendees will learn after a while what is good problem for a kata ;-) Regards, -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/ _______________________________________________ POST RULES : http://wiki.hanoilug.org/hanoilug:mailing_list_guidelines _______________________________________________ HanoiLUG mailing lists: http://lists.hanoilug.org/ HanoiLUG wiki: http://wiki.hanoilug.org/ HanoiLUG blog: http://blog.hanoilug.org/
