Lost in the library: The New York Public Library Digital Gallery

A tip from Jonathan Hoefler led me to the NYPL Digital Gallery, now fully searchable and browsable, with low resolution images free for non-profit use (including personal blogs, though not Wikipedia). Some really fascinating stuff, including a number of University of Virginia related items: detailed close-up shots of the pediments of East Lawn, the post-1895 Rotunda, the serpentine walls, two different views of the famous pre-1895 engraving showing the Lawn from the West with the Rotunda annex, a view of the full map of Virginia from which the 1826 engraving of the Lawn is drawn and a separate close-up of that engraving, other early engravings likely not drawn from life (since they don’t show the terraces on the Lawn) but including the pediment around Pavilion X, the exterior and interior of Edgar Allan Poe’s room on West Range following one of the Raven Society restorations of the room, and my personal favorite, pictures from a visit that Gertrude Stein and Alice B. Toklas made to the University in 1935, including a shot with faculty and students, the pair in front of a pavilion, and this nifty shot of Stein in front of the Rotunda.

I’m pretty sure you could kill hours just looking through this site–for me, the old photos from Newport News are just about as fascinating as the UVA material.

What are they betting on?

My friend and undergrad classmate Erik Simpson has been following an interesting trend on Intrade, the prediction market that allows predictive “bets” on realworld events. Specifically, Intrade’s prediction results were diverging from other predictive models, specifically those of fivethirtyeight.com. More research dug up the interesting fact that Intrade doesn’t agree with other predictive markets either. Yesterday Erik followed up these posts with the logical question: why not simply arbitrage the difference? If Intrade and the Iowa Electronic Markets are really efficient markets, there should be no persistent price spread, but since there is a price spread there’s an opportunity to make risk free money by selling on IEM and buying on Intrade, then reversing the trades after the election, when the outcome is locked. (As of this writing, Intrade has a 70% probability of Obama winning, vs. a 74.9% chance on IEM.)

The persistent difference in value can be explained by one of two market frictions: either there are one or more irrational actors who are making trades based on something other than rational economic decisions, or there is information asymmetry: the trader knows something that we don’t about the outcome of the election. I’m inclined to think it’s the former. But I don’t rule out the latter, for the reason that the GOP and its followers are starting to scare the hell out of me (anyone else wonder why someone shouting “Kill him” at a GOP rally wasn’t immediately brought in for questioning by the Secret Service?).

It’s not hard to see why the GOP might be frustrated at this point. The Democrats have done a superb job of keeping their powder dry, waiting until McCain really stepped up the smears to point out that he has deep roots in banking and real estate corruption through his membership in the Keating Five. This campaign has refused to roll over and play dead while smears and attacks were directed at them, and while they’ve played hard in return, it’s been to point out how McCain and Palin have specific unsuitabilities to deal with the issues in front of the country right now.

The downside of this campaign–one of the few really well contested matches we’ve seen in recent years–is that it doesn’t leave much room for discourse on the issues. I’d love to see Obama clear enough of the smoke to start talking about how we get out of this mess, but I think he’s going to be facing enough crap for the next few weeks that we won’t hear substantive proposals for a while.

Grab bag: All election, all the time

Technical Debt part II: Security debt

I wrote previously about “technical debt,” the concept that the decision to defer necessary technical work (adopting an updated version of a new component, refactoring code to reduce cruft, etc.) accumulates across releases until it absorbs a project team’s entire capability to develop code. You “pay interest” on technical debt because it’s much harder and consumes many more resources to make a necessary technical change the further downstream you get from the point where the change becomes necessary.

It occured to me today that there’s a specific flavor of technical debt, security debt, that is both more insidious and much easier to see in operation, because we have so many prominent examples of it. It might not have cost the developers of Windows too much more to make the OS more secure at design time, but some of the decisions were deferred, until the point where you had whole features introduced to address security deficiencies in prior features, and the six month long security push that postponed Vista’s launch while the team took care of outstanding security issues in the already-shipped version of the OS.

What’s interesting about security debt to me is that it balloons over time. My once-favorite mix sharing site, Art of the Mix, is a good example. The guy who developed it didn’t really understand SQL injection or XSS, or at least didn’t code defensively against them, and it’s become a hive of malware as a result–and is now flagged as a “reported attack site” and blocked by Firefox 3. So, to carry the metaphor to its logical conclusion, the site’s security debt drove it into a kind of “bankruptcy” when it proved susceptible to drive-by SQL injection attacks.

So how do you avoid incurring security debt? Learning good development practices is a good start; keeping up on the prevalent attacks–the current risk space–is another. But there’s one key thing to remember about security debt: in many cases fixing the underlying flaw that permits exploitation is far far cheaper than getting hacked, or even putting bandaids like web application firewalls in place.

Grab bag: A win, a history lesson, and a Smoot

Grab bag: Week’s end roundup

VP debate, the morning after

I livetweeted the debate last night (start, end) and was reminded of a few things in the process. First, writing about anything as it happens means you’re paying much closer attention to what’s said. I got more of a substantive understanding of Biden and Palin’s positions, a closer awareness of both of their stumbles and gaffes, and a much deeper engagement in the process than if I had simply been watching it.

Aside: why did I ever try to do liveblogging before there was Twitter? Even if each post is 140 characters or less, it’s still a superior user experience to a heavyweight blogging CMS.

Now, the downside of liveblogging the debate. I didn’t have my eyes on the TV very much and so missed some of the nuances–I had to see someone else’s tweet to realize that Joe Biden spent much of his time looking at the moderator rather than the camera when he answered his questions, for instance. And I think that there was a downside to paying such close attention to individual exchanges, namely: I came away without a feeling about how the debate had played overall. Oh sure, I thought Joe took it on substance, but as I tweeted late last night, I’m not 100% sure that’s what matters to the American undecided voter. And I can certainly see a scenario (reinforced by the GOP spin from last night) where Palin and McCain get a bounce because her performance wasn’t a miserable failure and because she came across as a folksy, relatively human person.

I kind of hope, though, that we don’t hear any more “maverick” after last night.

Update: Doc has the same concerns about the debate performances that I did. That doesn’t mean, btw, that I think that focusing on personality is right; just that the pragmatic view is to ask how well each debater played in Peoria.

Grab bag: No sign ban, Illustrator workaround, debate prep

Keep your hands and feet inside the car at all times…

…because something tells me this race is going to be a rollercoaster for the next few weeks.

Screenshot below from the excellent Election ’08 iPhone App, from Pollster.com and Slate. For a more nuanced view, look to the fine folks at Electoral-Vote.com, which shows Obama’s lead 338 to 185 electoral votes, with 15 ties. This high margin is pretty new in the race–back in early September, the lead was only about 100 electoral votes.

For more context, check out the historical trends on Electoral-Vote.com, where you can see what happens if you don’t count the states with a less than 5% margin of victory (answer: we don’t have a clear winner yet).

Grab bag: Bailout and iPhone notes

BSO and TFC: Brahms Requiem, September 26-27, 2008

As promised earlier, I thought I’d jot down a few thoughts about our performances of the Requiem this weekend, now that I have some distance on the music (meaning: the third movement fugue is no longer obsessively pounding in my head).

I have a long history with the Requiem. I first almost performed it in the late 1990s with the Cathedral Choral Society in Washington, DC, but a family death took me away from the performance after I had almost completely learned it. I finally got a chance to sing it in 2004 with the University Presbyterian Church choir in Seattle, but in English and with a bad head cold. The first time I performed any of it in German was our tribute to Lorraine Hunt Lieberson at Tanglewood in 2006, when we sang the fourth movement (“Wie lieblich sind deine Wohnungen”).

But of course, any performance of a full work with the Tanglewood Festival Chorus is different from any prior performance of the same work, for the simple reasons that (a) you’re singing with one of the best orchestras in the world and (b) you’re doing it from memory. In this case, that’s seventy-five minutes of German, including two bloodying fugues, by heart.

So my perspective on the Requiem has two aspects: one rather like a marathoner’s perspective regarding his last run, and one of a participant in the creation of great beauty.

From the former perspective: pacing is the biggest problem in singing the Brahms, because there are three Heartbreak Hills. The first and fifth movements are calm and fairly easy to sing, the fourth and seventh are louder but also even tempered. But each of the other movements has its own unique challenges. The second movement has those stretches of the funeral chant (“Denn alles Fleisch es ist wie Gras…”) that are sung over the full orchestra at forte volume, down in the bottom of everybody’s tessitura. And then there’s the “Aber des Herrn” at fortissimo, followed by a nice fuguelike section which is thick and inspires a certain tendency to shout. And the third and sixth movements have full-on fugues and climaxes–they’d both be finales in a lesser composer’s hands. Plus, even in the low and medium movements, you have challenges — for the tenors, there’s the high A near the end of the first movement and the final “wie lieblich”, which calls for the tenors to do a very controlled crescendo at a very high point in the range while keeping extremely beautiful tone. So the profile of the work from an emotional perspective is low – high – very high – moderate – low – very high – high, but the technical difficulty profile is basically high – very high – very high -high – high – very freaking high – high, and you have to really husband your emotional and physical energy accordingly.

The alternative: you hit the wall sometime around the sixth movement, the real uphill battle of the work, before you even get into the fugue. And in that fugue, as our director said, there is inevitably “blood on the walls” in every performance thanks to the demand on the singers and the difficulty of the preceding music. So the secret is to remember what’s ahead and never, ever, ever go full volume. If the director asks for more in a climatic crescendo, focus the voice up into the face so that it projects more clearly, rather than simply opening up to full vocal throttle.

From the second perspective: I’ve never sung in a performance where every chorister was so on top of the music, and so together–total telepathic connection from person to person. And every one of them singing right to the limit of the safe range of the voice, without going into the danger zone, thanks to lots of “marathon” experience. And with the improved acoustics of Symphony Hall, being able to hear other voice parts as though they were standing right next to you. So performing it was a joy. I can’t pretend to be able to provide an objective review of our own performance otherwise, but if the hall was enjoying it half as much as we were, it’s no wonder they applauded as vigorously as we did.

Grab bag: Bailout out

Brahms Requiem: gearing up

I’ve been in rehearsals all week at Symphony Hall for the Tanglewood Festival Chorus’s first concert of the 2008-2009 Symphony Hall season, the Brahms Requiem with the Boston Symphony under James Levine. It’s an amazing work–I’ll try to describe it in more detail after our performances. But the two really amazing things for this weekend for me are the same things that Jeremy Eichler flagged in his review of Wednesday’s season opener, namely, Levine himself and the windows in the Hall.

Losing Levine to two months of cancer treatment after the opening of the Tanglewood season was a blow to audience and performer, although some of the resulting performances under guest conductors were still pretty spectacular. But it’s great to have him back and he is as energetic as ever.

The clerestory windows … well. Eichler gives the background in his article (part of the original design of the hall, they were covered over during World War II to comply with blackout requirements and never reopened). But what he doesn’t mention is the effect on the hall’s sound. The window openings had actually been plastered over, and the removal of all that plaster and introduction of glass (albeit a special glass that doesn’t resonate) means that there’s a new brilliance on the sound in the hall. Levine remarked on it, our director remarked on it, and it was even apparent on the stage in the reflected sound during our rehearsal. We’ll see tonight whether it makes as much difference when the hall is full of people.

It certainly has a striking visual effect, especially for a daytime rehearsal. I only had my iPhone on me so the picture I got was pretty poor, with lots of streaks from the light sources running through the pictures, but you can still see how alive the hall looks now.