As it turns out, there are quite a few composition contests, calls for scores, conferences, and other opportunities available to composers each year. And, following the advice of Eric Whitacre, I try to submit things as often as I can. But I kept falling into this pattern:
This obviously didn’t work that well for me. So at the beginning of this academic year, I decided to try something new. I thought, if I can somehow automate (or nearly automate) the contest submission process, then I’ll be spending less time sending off compositions (or rather, less time not sending off compositions) and more time composing. Or watching police procedurals. Or both! So I built HOE.
The Hammer Opportunity Engine or HOE is essentially a composer’s to-do list on steroids. It tracks composition opportunities, which pieces to send, whether the deadlines are postmark or receipt, and it prints the mailing and return address labels, all coded with QR codes. It plugs into Hammer’s composition database (which drives kylevanderburg.com) so new compositions are added automatically. And it basically reminds me incessantly when submissions are coming due.
While I’m sure I could go on about how HOE works, it’s probably more interesting to talk about what I’ve learned by using it. Here’s a list of things in no particular order:
So there it is. My programming geekiness meets my composerlyness.