What I like

  • It was interactive
  • Coding dojo
  • Green bar refactoring
  • Like "every IF kills a little white rabit"
  • Learned to try to fix tests not by adding code but by changing the behaviour through the constructor
  • Hands-on
  • Good humor
  • Hands-on approach is great
  • Explanations while working on concrete example
  • Involving audience
  • Think about how it first and find refactor so that new change first before making the actual change (start with green first)
  • Create new objects instead of changing existing objects
  • Live experience of what happens when adding features when the tests fail
  • Good also for rusty programmers like me
  • Well-chosen example (especially for a one hour dojo)
  • Good reaction to the public's comments and suggestions
  • See code exampe
  • Practical
  • Can apply this on Monday
  • Concept
  • Interesting way to see how you can solve the if-problem quite readably
  • Live coding
  • TDD demonstrated, composition
  • Studying code
  • Greate code craftsmanship
  • Funny
  • Good examples, well presented
  • Interesting rule
  • Refactor before implementing new stuff
  • Practical
  • Combination of principles (e.g. composition over inheritance)
  • It presented a nice approach to TDD with earlier design into the code, producing nicer code earlier in the process

To improve

  • Add more examples of code where the open/closed principle can be used
  • When the developers aren't up to speed with java or Apple the coding is slowed down
  • Try to improve your English and try to relax, it's a great idea
  • Some more info and examples about the open/closed principle
  • It's a pity the participants didn't participate much: whay about a prize for the best contribution or something similar?
  • Summarise handy tips on a sheet which could be a Conclusion slide
  • Timed coding, everyone needs to code
  • Takes long (sometimes) to let others program<; if you do it yourself with feedback of the group it will be better
  • Two code examples were given. It would be nice if they had had less similarity - the point would have come acrosss more convincingly
  • Not very deep, expected some examples, more profound. Would benefit from a bit more chaos :-)
  • Everyone codes!
  • Timing: great save but you could have take over faster, to enable a second demo
  • Intervene when dojo gets sidetracked
  • Present one ready practical example before and after the exercise