If the source code is in the wild, Goldman Sachs is forced to stop all related real-time trades, because their strategy is completely exposed, and once somebody exploits it, they will lose money really quickly. (Just imagine how many transactions they can make per second, and imagine every one of those transactions lose some money in average.) That means they get forced to leave the market until they develop a new trading system, or at least, re-develop their strategy. That costs a lot of money because they have to stop doing investments and leave the money some place safe. — well, that might at least explain the funky HFT statistical anomolies

… and then let’s go home.  My apologies for trying Doomers’ patience on this one.  I’m still "re-retired," but thought the off-topic Goldman Sachs code story arc was too important to leave alone.  Unless something really hairy comes up in the next while I’ll try to limit myself to occasional links on the sidebar now.

The above is from the comment thread under the only Aleynikov story on slash/dot to now.  That long thread serves as a sort of tutorial running through how leaking the GS code might hurt their present business model.  I’m sure there must be some discussion in the relevant Open Source development mailing lists on what busting Serge means to similarly employed S/W developers on a personal basis, but it’s been so long I don’t even remember what those mailing lists are.


UPDATE (7/17): Holy presumption-of-innocence, Batman!  Somethin’s fishy about this NYT Op-ed.[1]

Now maybe Mikie wrote the whole thing, and maybe he’s sitting on that oyster barge of his fuming at the Old Lady for Joycing up his text; ’specially that header bit.

But if the next Docker hits the planks is some sweet plea deal where Serge gets a slap-in-the-wrist  fine and couple nice vacation months away from the kiddies & diapers, suspendered Damocles-style long as he don’t rock the boat no more,[3] then The Castle here’s gonna suspicion maybe the S.S. Bada Bling got better stuff to do this fall than perform "Disc Loss … Sure!" [2] up against a dozen random piers with some old fed court judge scribing the reviews.


Stand by for a longish subprime post soon, and I’ll try once more to refocus on housing for a while, and refrain from further comment-posts (exception to that being venting at the head of the weekly H.4.1 update posts on Fridays).

………………………….

LATER: OMG!!! Secret’s out …

Based on the Rolling Stones article [rollingstone.com] I was able to reverse engineer the core Goldman Sachs trading algorithm:

#include
int main( int argc, const char* argv[] )
{
pump();
dump();
}

Apologies to indent purists everywhere.

—————————————

[1]: "Steal This Code", by Michael Osinski, New York Times, July 16, 2007.

[2]: "Brokers pilot yachts; investors wish for rowboats", by Lauren Rudd, Herald-Tribune (SW Florida), July 17, 2009.

Such an infraction might have been overlooked had it not been for the countless hours and millions of dollars Goldman spent developing the software, designed to detect large order positions ahead of their execution. In other words, the software enabled Goldman to essentially engage in high-tech front-running.

[3]: "Demons in the machine", Andrew Leanard, Salon / Business Spectator, July 18, 2009.

In this business, it’s all about having the best hardware, smartest software, and maximising every possible technical advantage – such as physically locating your computer servers as close as possible to electronic trading systems so as to save every possible millisecond.