the $440,000,000 codeing error!

[anything I don't mind]

haha, you would have thought they could have just pulled the plug after noticing the problem 5 -10 mins after starting it. Seems a bit suspect, seems a bit unlikely to be an accident. I don't know why someone would want to do that though.

 

[GravyMonster]

Why are you using 14 year old software anyway???

I'm not now, but I was 11 years ago.

 

[StriderX]

Good thing what you say isn't correct then! The article states that the "lost" monies is enough to wipe out any profit Knight made in 2011 and seriously affect its future.

Somewhat important I'd say!

I meant in the entirety of the system, not this useless firm.

 

[HungryHippos]

No There was a backup thankfully, so we only lost that days transactions, which was about 30,000 records. Got a major *******ing and an insta-written warning though, all for forgetting a WHERE clause.

Woops, I would have used a transaction though. At least it would have told you "60 million rows affected" then you could just do a rollback.

 

[wannabedamned]

I'm not now, but I was 11 years ago.

haha

Not sure why, but that tickled me

 

[Adam]

Reading the articles on this, isn't Knight Capital in danger of being bankrupt?

Yes, they are in trouble. They got hit hard by the facebook float as well.

 

[Theophany]

I'm not now, but I was 11 years ago.

So was your 14 year old software only 3 years old 11 years ago then?

 

[TNGL]

$440m, lul.

 

[MADMAN]

oh man i need that error on my bank statement

 

[Judgeneo]

Why did they let it run for 45minutes? Surely they could have shut it down far quicker than that...

 

[estebanrey]

I'm not now, but I was 11 years ago.

Ahh furry muff, way before my time (SQL knowlegewise I mean, I was obviously alive then )

 

[scorza]

With spelling like that he's probably a programmer.

Not for me. Dodgy spelling in source code is a performance management issue.

 

[Deleted member 77746]

Youch.

Makes me feel better about my biggest mistake; deleting 60million transactions from a SQL database.

No There was a backup thankfully, so we only lost that days transactions, which was about 30,000 records. Got a major *******ing and an insta-written warning though, all for forgetting a WHERE clause.

They may well do, but I can tell you now SQL Server 7 doesn't

Should have been sacked.

 

[Stev]

There will be a small charge for the DLC that fixes this error

 

[FabienO]

No There was a backup thankfully, so we only lost that days transactions, which was about 30,000 records. Got a major *******ing and an insta-written warning though, all for forgetting a WHERE clause.

lol. "

School-boy error "

As my Boss would say. I've known devs who've taken down businesses and blamed it on hardware tbf