What I liked:
- it is executable, working code
- passion, enthusiasm, confidence
- topic
- simple example
- idea
- stepwise TDD + iterate and improve
- very practical demonstration
- discussion/ debates on the advantages + disadvantages
- the energy of presentors
- descriptive specification
- IDE, use of dynamic language, use of tools new to me
- clearity of tests: spock
- simplification of test: DSL/Geb
- I saw some grails
- good speakers
- seeing a bit of grails (compared to Rails, which I'm familiar with)
- debates
- the accuracy of the problems that popped up
- proficiency of the speakers
- adapting to remarks
To make it perfect:
- prepare better
- faster pc
- describe the purpose
- describe the tool(s)
- faster machine
- interesting = valuable example
- clearer spec
- include the audience more
- why is using spec language usefull? It seems to take quite some time.
- unix/java/grails seems a specific platform tool? What's equivalent on Windows/.Net?
- skip setup and dive in more complex things right away
- I'm sold on TDD, but not on BDD... If not directly used by customer, what's the use?
- for me, it was too limited content
- could be slightly longer, the really interesting stuff came towards the end. Mabye shortcut the start to get to that part more quickly.
- test code seems unclear
- clear tests
- know what to expect (failure or success and why)
- longer
- choose another setup for session rooms. Not really good for given feedback --> to far from sessins given
- grails and groovy are not usefull in Enter
- show more why TDD is useful to me, convince me that these kind of tests can be written by anyone else than a developer
- faster test execution
- prepare your testing path a little more
- faster computer!!! :-)
- I joined late; can't really tell :-)
- shorter feedback loop
- achieve something more representative. Maybe be more directive
|
