When I saw my first episode of Monster Garage, I thought it was just tomfoolery. After all, why would you want to waste the talents of a team in transforming a Chevy Impala into a Zamboni? Alright, so it's great fodder for Hollywood. But in building these crazy contraptions, I think the team gains invaluable experience. It's not often we get to step outside the box and experiment with taking our skills over the top. Indeed, we're usually practicing our craft on the job when failure is not a very good option. Trying new things is incredibly risky in these situations. Instead, what might happen if we had an opportunity to practice with impunity? How might stretching our skills to build something with no obvious business value help us when the business is on the line?
And to think that the "real" programming community has for years been chiding Perl for doing this very thing. Why do we need a datetime module to report babytime, or one to translate your sourcecode to sequences of whitespace or repetitions of everyone's favorite slayer, or any of the other fun but weird distributions on CPAN? (See most anything under Acme:: for more...)
Of course we don't need these to solve a problem right now, nor will we likely ever. But serendipity favors the industrious, even if it's occasionally difficult to separate the industrious from the whimsical and just plain silly. And maybe you shouldn't even be separating them. Maybe they can't be separated.
Outside the box is lateral thinking, and one way to get there is to be silly. A few years ago I happened on a C-SPAN Booknotes interview with Toni Morrison and the interviewer asked her what piece of advice she most often gives young authors. Her answer? "Have fun." Play with rhyming, play with not rhyming. Mess with style, form, everything. It's a useful way to learn, especially when you get stuck. You don't need to publish everything, just think of it as exercise.
Lots of discoveries have been spawned from the motivation to make money. Nothing wrong with that. But I wonder how many have been inspired by downright filthy aims? Or how many have come about because someone wanted a new way to get high? The thing about discoveries is that once they exist and are accepted, the motivation becomes secondary and eventually irrelevant.
Perhaps working on one of these crazy CPAN modules just filled some downtime. Maybe it bridged a frustrating gap of coder's block. Maybe it was created from an offhand IRC comment, or an idea from a dream. Whatever. While you can argue that maybe these things should be kept private, that's not the opensource way. Keeping them private would be clean and tidy but that's not part of the conversation we have when we publish software. Silly discussions are part of that conversation, and IMO Perl is a stronger community because of the variety of its conversations.