News for hackers. Stuff that matters.
Re:Ditching Excel for Python in a legacy industry by konjin on Wednesday December 30, 2020 @07:36PM (#25588138)
My first job was cleaning up the mess that was caused by hard coded yahoo finance urls in spreadsheets. One of them died, no one noticed and it cost the company millions of dollars in bad trades over three months.
Re:Ditching Excel for Python in a legacy industry by Closi on Wednesday December 30, 2020 @07:40PM (#25588181)
You could automatically import a table from the web into the sheet, or alternatively create some custom data types for currency conversion.
Re:Ditching Excel for Python in a legacy industry by konjin on Wednesday December 30, 2020 @07:48PM (#25588232)
Or you could act like you're responsible for tens of millions of dollars and hand it over to someone who can make sure it doesn't blow up.

"We don't need to hire an electrician to wire up the office, I did my garage using uninsulated wires and it works perfectly!"

Re:Ditching Excel for Python in a legacy industry by Closi on Thursday December 31, 2020 @04:00AM (#25590924)
The guys handling millions of dollars should be trained in finance / accounting, so they aren’t untrained.

Handing over to IT usually means their flexible spreadsheet that they can change as they require, turns into an expensive and inflexible black box that only IT can change and that doesn’t integrate with the rest of their decisions. Also the new solution also probably has errors and pulls currency info from the same endpoint. Excel isn’t perfect, but it’s used for a reason.

To use your analogy, You can wait for an electrician to change your lightbulb, but that means your going to be working in the dark for longer.

Re:Ditching Excel for Python in a legacy industry by konjin on Thursday December 31, 2020 @06:53PM (#25598757)
Lightbulbs do not generally cost millions when they go out.
Re:Ditching Excel for Python in a legacy industry by listenallyall on Thursday December 31, 2020 @12:06AM (#25589780)
are you suggesting programmers don't hardcode URLs in quick-and-dirty (and sometimes, even production) Python scripts/code?
Re:Ditching Excel for Python in a legacy industry by konjin on Thursday December 31, 2020 @02:10AM (#25590343)
I'm suggesting they have logs.
Re:Ditching Excel for Python in a legacy industry by listenallyall on Thursday December 31, 2020 @02:39AM (#25590507)
logs of what? if a programmer hard-codes URLs, you really think they are following best practices elsewhere? further, how do logs help get back the millions of dollars that were lost?
Re:Ditching Excel for Python in a legacy industry by konjin on Thursday December 31, 2020 @06:55PM (#25598771)
Yes, logging with email alerts means that when a catastrophic error is encountered you'd know about it, instead of it being hidden for months.
Re:Ditching Excel for Python in a legacy industry by listenallyall on Friday January 01, 2021 @09:08AM (#25603341)
LOL! as I already stated, a weak coder isn't going to implement best practices for logging. At best, he hard-coded his own email address to receive an alert, however, this also goes unnoticed, since, as you stated initially, he's dead.

Look, whatever company this was, was relying on YAHOO as its data source for making million+ dollar trades -- not Reuters, or Bloomberg, or JP Morgan, but YAHOO -- and then, for MONTHS -- not hours, or days, but MONTHS -- nobody in its finance department or trading desk or whatever happened to notice that the incoming data feeds were not matching up with quotes from counterparties, market makers, CNBC, colleagues, Wall St Journal? Does this company not have auditors? A CFO? Any IT oversight whatsoever? I'm sorry to say that this particular company's problems are rooted much, much deeper than the loss of a particular Excel guy.