Re:Ditching Excel for Python in a legacy industry
by etothepii on Thursday December 31, 2020 @05:48AM
(#25591543)
If the code was stored in source control with a separation between dev and production the intern might be able to raise such a Pull Request but it would never get approved without oversight from someone more senior. This Code Review process is almost completely impossible in Excel.
[ Parent
| on HN ]
Re:Ditching Excel for Python in a legacy industry
by pjmlp on Thursday December 31, 2020 @08:45AM
(#25592611)
That is a big if.
Office has source control management via SharePoint integration.
Re:Ditching Excel for Python in a legacy industry
by zentiggr on Thursday December 31, 2020 @11:11AM
(#25593933)
... and then you have two problems. I have never seen an environment converted to SharePoint that didn't suffer badly from the conversion.
And the Excel vs <other language> source control issue isn't history, it's "go ahead and try to diff between two versions of an Excel sheet" vs "diff two versions of that source file".
Unless I've never heard of the tool that can digest two Excel sheets and tell you what formulas differ, or cells. Please correct me, anyone who knows of one.
Re:Ditching Excel for Python in a legacy industry
by zentiggr on Monday January 04, 2021 @01:12PM
(#25635467)
Late response over the holidays, but honestly thank you. In years of Excel usage, I've never stumbled on that or had anyone mention it.
I will look into that as Excel 2016 is one of my current required work apps.