Re:Ditching Excel for Python in a legacy industry
by sam_bristow on Thursday December 31, 2020 @02:41AM
(#25590515)
I remember hearing about a mythical spreadsheet floating around for modelling something to do with our national grid a few years back.
It would take about 12 hours to calculate, and would error out before finishing about 30% of the time. It needed to be run once a day for something reasonably important.
I don't use Excel much these days, but I do point people to a video if they do plan on doing anything:
* [You suck at excel - Joel Spolsky](https://m.youtube.com/watch?v=0nbkaYsR94c)
Re:Ditching Excel for Python in a legacy industry
by rvba on Thursday December 31, 2020 @08:36AM
(#25592527)
Someone who does not use Excel nice will probably make spaghetti code as well.
Re:Ditching Excel for Python in a legacy industry
by larrywright on Friday January 01, 2021 @02:22PM
(#25605900)
I'd rather reverse engineer spaghetti code than a spaghetti Excel spreadsheet.
Re:Ditching Excel for Python in a legacy industry
by JackoM on Monday January 04, 2021 @11:46PM
(#25642219)
Most probably because you do not know Excel !?
But for someone who do know well Excel and understand finance concept it'd be easier to understand the spaghetti Excel spreadsheet and find where it doesn't work properly !
Re:Ditching Excel for Python in a legacy industry
by empthought on Saturday January 02, 2021 @06:57AM
(#25612189)
You’ve been lucky with your spaghetti code experiences, then.
Re:Ditching Excel for Python in a legacy industry
by larrywright on Saturday January 02, 2021 @06:17PM
(#25617589)
At least with spaghetti code I can set a breakpoint or add print statements and get an understanding of the execution path.
This cannot be stressed enough. I've outlived generations of finance teams at many startups, and I've seen firsthand the masterpieces/abominations left behind in Excel. Imagine a dozen sheets with ad-hoc queried data copy/pasted from System A/B/C/D into Excel, with formulas that feed formulas that feed formulas. Sometimes columns are inputs (seasonality adjustments for monthly forecasts), sometimes their outputs (modeled growth * last year * seasonality adjustment) and more often than not their right next to each other and maybe they have different cell background colors or a black separator line. Maybe.
And this is just finance. For many e-commerce businesses, planning is done in Excel with equal zeal.