Most everybody I know (in the field) is in disbelief concerning the length of time the Knight disaster unfolded over. I've had systems "loop" in BAD ways, but n

Most everybody I know (in the field) is in disbelief concerning the length of time the Knight disaster unfolded over. I've had systems "loop" in BAD ways, but never for more than 1-3 seconds. Safeties are paramount in the field. There's many layers of protections to avoid *ing yourself. Most of these are deployed in ways that are not terribly expensive on the 'critical path' -- that said, there are a LOT of people doing REALLY stupid things in the field. (As there are in any field, it's just more 'scandalous' when an error in a financial application occurs) Algorithm implementation is largely trivial, and the high pricetags paid developers in the industry are usually for specific engineering skills along with the semi-requirement that developers be 'all-hands-on-deck' when the situation calls for it. (There's a bug in the new strategy...well you need to fix it before tomorrow's open etc) At least, that's how I see it.