News for hackers. Stuff that matters.
Re:The Idiot's Guide to High Frequency Trading by jarrett on Friday April 04, 2014 @03:02PM (#7533562)
There is still risk. Even if you never lose money on a trade, your firm can lose money. You're paying fixed costs such as colocation. It's conceivable that all your trades are profitable, yet the sum of all those profits is lower than your fixed costs.

That becomes more likely for any given firm as the competition increases. Spreads get smaller; there's more competition for any given trading opportunity. For each firm, that can mean declining profits per trade and declining numbers of trades made. When the product of those two numbers gets too low, you're in the red.

Re:The Idiot's Guide to High Frequency Trading by foobarqux on Friday April 04, 2014 @03:07PM (#7533600)
Or you can blow up like Knight.
Re:The Idiot's Guide to High Frequency Trading by wglb on Friday April 04, 2014 @03:43PM (#7533832)
Knight had test code that got flipped into production.

Worse, they ignored many alarms as the company was sinking.

Re:The Idiot's Guide to High Frequency Trading by fr0sty on Friday April 04, 2014 @04:23PM (#7534082)
> Knight had test code that got flipped into production.

This is not correct. Read the SEC report on the incident if you have time, it is pretty in depth: http://www.sec.gov/litigation/admin/2013/34-70694.pdf

The short-version is that they re-used a parameter from an old feature and one of the production machines was not updated so the re-used parameter re-activated the old feature instead of the new one. Furthermore, A refactoring of the code had left the old feature on the wrong side of the share accounting code so the system was not keeping track of the orders it was putting out.

Re:The Idiot's Guide to High Frequency Trading by wglb on Friday April 04, 2014 @06:05PM (#7534727)
Thanks for that.

But still it was not any kind of market or trading risk that blew them up--just a litany of control failures and bad code.