What I liked

  • The interaction
  • Concrete examples
  • The discussion generated
  • The format, comparing code made me think
  • The explanations on the code to make them clear
  • The topic
  • We're looking at actual code
  • Forces us to find ways to talk about code
  • Code! A real XP session
  • Nice comparison of several frameworks
  • "If your tests smell, it's probably your code that stinks"
  • Reading code
  • Collaborating comments
  • Good to talk about code
  • Code cases
  • Interesting discussion and examples
  • Always nice to learn test tips using real examples
  • Interesting discussion
  • Lots of conflicting opinions
  • Examples were very interesting
  • Learned several techniques in a short time
  • Discussing in small groups helps understanding
  • Lots of smart people discussing -> interesting
To make it perfect

  • More time for discussion and to show the kata (session could be 1,5 hours)
  • Don't encourage discussions on opinions, encourage discussions on experience
  • Favor for coding over discussion
  • Link it more closely to "Clean Code"
  • Find a way to make the interaction more energetic
  • Fit in the timebox :-)
  • Make it 90 minutes
  • Less Kata
  • Time management
  • In was mostly focused on "tests can improve design", but the title of the talk suggested broader scope
  • Use Python instead of java ;-)
  • Need more time!
  • Not enough time for discussion
  • Clearer references to "Clean Code" book
  • "Gathering": was difficult to remember what the different examples were again. Could you display the posters while explaining?
  • Cheating! There were two sessions (the first one was finished at 12:00)
  • Kata: slow down! Explain a bit more what you already have at the start