In Higher Order Javascript, I introduced Streams and showed how to use them to implement a lazy sort. I think that's neat all by itself, but it's not directly useful in the asynchronous, event driven execution environment that is the average web page. We'd like a structure where we spend less time twiddling our thumbs as we wait for force to return something to us.

To my surprise, several people have asked for the slides from my Øredev talk on Higher Order Javascript, and I’ve followed my usual practice of saying “Sorry, no”. Slide decks are a terrible teaching medium - they’re fine if they come with the presenter, but if they contain enough information to read as if they were a book, then I’m prepared to bet that they made a terrible presentation. Good presentations have a synergy; slides illustrate what the speaker is saying and neither the speech nor the slides should really stand alone. After all, if either could, why bother with the other?

Crikey! What an intense few days.

Last Friday, I got some email from Giles Bowkett saying that he’d had to flake on a conference in Sweden and could I take his place. The brief was to “be interesting, and I know you can nail that in your sleep”.

Last Saturday, I read it. And being flattered by Giles’s silver tongue answered to say “Probably, when is it?”.

http://soundcloud.com/pdcawley/tamlyn

http://soundcloud.com/pdcawley/the-blackbird

http://soundcloud.com/pdcawley/composed-in-august

https://soundcloud.com/pdcawley/the-wayworn-traveller

While I was at OSCON I found myself chatting with various non-perl and ex-perl folks and many of them had the same impression of Perl as a great language for hacking out short scripts to get stuff done, right now and possibly under severe time pressure. For these people, those scripts would very rapidly become unmaintainable. And it’s easy to see why they came to that conclusion. Perl was originally designed and implemented by a systems administrator as a tool to make his every day tasks easier so there are a bunch of shortcuts and defaults that do exactly that - make Larry’s life in 1987 easier. Which is great when you’re whipping up a script to meet an immediate demand, but horrendously cryptic when you look at it later.

http://soundcloud.com/pdcawley/little-musgrave

http://soundcloud.com/pdcawley/come-write-me-down

http://soundcloud.com/pdcawley/false-true-love

http://soundcloud.com/pdcawley/how-can-i-keep-from-singing

If you’re interested in the repertoire project, here’s my current rules of engagement for recording for it:

• One Song
• One Mic
• One Take (by which I mean no comping or overdubs, not “only one attempt”)

So far, everything has been recorded using FiRe, a dead simple field recording app on the iPhone/iPad and uploaded pretty much directly from the phone to SoundCloud, though I am thinking of switching to using my BandCamp account because, although the player may not be as pretty, the site is free. SoundCloud keeps nagging me to switch to a paid account if I want to do things like make everything downloadable or see more advanced player statistics. Very annoying.

http://soundcloud.com/pdcawley/the-grey-cock

http://soundcloud.com/pdcawley/the-pretty-ploughboy