One of the things that has always bothered me about training courses is when trainees get taught to do something that "will only make sense later, when you do it".
For example, TDD, BDD - a newcomer to testing, in rails or whatever, would see very little value on adding tests to the Build-A-Blog application the class makes during the training - to them, it's a waste of time, the code gets written, the tests do not help. Sure, you could inform them about the importance of writing tests, "just use your imagination!", "I always write them, so should you!", and how, with a complex application tests actually help you write code, make sure things don't break, and all the other verbal words of wisdom - but very rarely would they get to use and see this importance first hand. That's the tricky part - if you want to train people about TDD and BDD, and the importance of it, in a *practical setting* - then you absolutely need *practical exercises* - and not just add a few tests to the three basic models of the example simple application. Now, I'm guessing because I've never seen such a thing, but perhaps, shove a complex application, with existing tests, and get them to add some additional functionality? Tim I'd also be up for guinea pigging too. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "NWRUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/nwrug-members?hl=en -~----------~----~----~----~------~----~------~--~---
