What I liked about it:
- +- the same insights that I gained doing TDD with Mockito, just explained better, by using design principles
- more ignoring insginificant diff between agile methods, generalize appropriately
- explanation of the context
- good structure in presentation
- using code to demonstrate/clarify explanation
- clear explanation
- good topic, not new, but certainly interesting
- explanations
- level of detail
- practical relevance
- "TDD vs good developer effects"
- good quotes
- focus on context
- good philosophical view on TDD (but could be shorter)
- real life experiences instead of just theory
- solid principles are always good to refresh
To make it perfect
- te weinig concrete voorbeelden om te overtuigen; veel minder praten/herhalen van wijsheden en meer tonen: code voor / code na
- make it more a doing session
- good tips and tricks
- design patterns
- sometimes difficult to understand (practice english more?)
- visualise more
- more cohesive story, maybe some more slides illustrating points. Not only proposition - quote - conclusion
- more code examples
- you explaine the different mocks and designs well, but will be even clearer if you indicate on the slide or write down what you explain (ISP = Interface Segragation ...)
- I did like the quotes in the beginngin of the presentation, but there are so many that they distract from what you are saying
- I would prefer to skip the history and delve deeper into the why's
- add something interactive
- interaction with public?
- big part was about promises of TDD and what you observed after TDD, I expected more practical usage of mock objects to see if I do it in a similar way
- spend less time per statement
- what is your goal (explain, motivate, ...)?
|
