Oh no, you're thinking, yet another cookie pop-up. Well, sorry, it's the law. We measure how many people read us, and ensure you see relevant ads, by storing cookies on your device. If you're cool with that, hit “Accept all Cookies”. For more info and to customize your settings, hit “Customize Settings”.

Review and manage your consent

Here's an overview of our use of cookies, similar technologies and how to manage them. You can also change your choices at any time, by hitting the “Your Consent Options” link on the site's footer.

Manage Cookie Preferences
  • These cookies are strictly necessary so that you can navigate the site as normal and use all features. Without these cookies we cannot provide you with the service that you expect.

  • These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.

  • These cookies collect information in aggregate form to help us understand how our websites are being used. They allow us to count visits and traffic sources so that we can measure and improve the performance of our sites. If people say no to these cookies, we do not know how many people have visited and we cannot monitor performance.

See also our Cookie policy and Privacy policy.

This article is more than 1 year old

A Reg-reading techie, a high street bank, some iffy production code – and a financial crash

We're not saying the last one is connected, but....

Code Red Though there has been much handwringing and finger-pointing over what caused the last financial crash, one Reg reader experienced at first hand the type of muppetry that no doubt played a part.

The reader, who requested anonymity and so shall be called Bob, was a bright-eyed new recruit at an unnamed UK high street bank. His duties included working on the risk management system.

Because he was a conscientious chap, Bob was reviewing some production code when he came across this gem (reproduced in pseudo-ish code):

foreach POSITION in TRADER.POSITIONS
{
    TOTAL_EXPOSURE = POSITION.EXPOSURE;
}

Eagle-eyed readers will note a critical character missing, namely a "+". Rather than totalling up a trader's exposure on the markets, the production code simply returned the last position, giving what would likely be an entirely false report on the bank's total exposure.

Bob took the code to his manager, who turned a shade normally reserved for the recently deceased before ushering Bob out of the office, assuring him that the problem would be dealt with and uttering the words: "Speak of this to no one..."

Apparently a scene resembling the arrival of the Child Detection Agency of Monsters Inc. followed, and the codebase was rapidly scrubbed. Bob, however, didn't stick around. He wisely moved on within a few months, leaving the final outcome shrouded in mystery. ®

Wanna share a code screwup? You can contact your humble vulture, here.

 

Similar topics

TIP US OFF

Send us news


Other stories you might like