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?
[ Parent
| on HN ]
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.