Stuff with the Perl Foundation. A couple of patches in the Perl core. A few CPAN modules. That about sums it up.
At Portland Perl Mongers, we've had chromatic give talks about tests and Schwern rant about tests. Since many people still aren't testing, I had an interesting idea, but now I have to put my money where my mouth is.
In October, I'll bring my laptop and have no presentation whatsover. Instead, I'll take an idea for a module from the assembled mongers (I'll have a backup idea or two if the ideas are not practical) and I'll sit down and create the module, in front of them, using test-driven development. Further, it's going to be mathematically challenged pair programming as I'll invite everyone to kibitz, er, pair, and we'll build a module together with me explaining things as we go. What an
Doing tests... (Score:1)
Re:Doing tests... (Score:2)
Interestingly, I was at Powell's Technical Bookstore [powells.com] the other day and I noticed that not only was "Perl Medic" the best selling Perl book, it was also one of their top selling books over all. Amusingly, their top Java book's subject was about how to avoid bloat in Java programming.
Re:Doing tests... (Score:1)
Hm, was that second book also Perl Medic?
Re:Doing tests... (Score:1)
Then you need to go see Ovid's talk! The point about TDD is the fact that it helps you drive your code's design, getting a good test suite out of it is just a pleasant side effect :-)
Go for it. Live TDD demos are good! (Score:1)
I've done it a couple of times when running tutorials for some companies.
Random advice:
Re:Go for it. Live TDD demos are good! (Score:1)
Have you found any "assignments" be more successful and pedagogic than others? Anything to avoid?
Re:Go for it. Live TDD demos are good! (Score:1)
I guess pick something that you can get up and running quickly, but can expand easily if you have time. I found that it can be quite a shock how much slower TDD is when you have to explain as you go.
Some of the things I've used:
Re:Go for it. Live TDD demos are good! (Score:2)
I did this sort of thing for Perl University (O'Reilly's travelling road show that they only did for a year). It was a big hit.
I had a constraint though: I had in mind a handful of problems, and they audience could pick one of them. That way I didn't get stuck on something I couldn't work my way out of.
Go TDD Go! (Score:2)
I've done the "build a module from scratch" to demonstrate the parts that go into it. Module::Starter basically started from there.
--
xoa