News for hackers. Stuff that matters.
Re:Ditching Excel for Python in a legacy industry by quietbritishjim on Wednesday December 30, 2020 @07:06PM (#25587919)
In Excel there's a toolbar button to toggle showing formulae rather than their results. I realise this doesn't counter your overall objection, but it does mean chasing down logic isn't quite as bad as having to select individual cells one at a time.
Re:Ditching Excel for Python in a legacy industry by ogre_codes on Wednesday December 30, 2020 @07:24PM (#25588050)
I mean... sure? There are a fair number of ways you can mitigate these issues, but the way spreadsheets are structured does not lend itself to structured/ well managed code.
Re:Ditching Excel for Python in a legacy industry by DavidPeiffer on Wednesday December 30, 2020 @09:30PM (#25588941)
I fully agree, things can get out of hand in spreadsheets. I've built my fair share of such spreadsheets, and as penance, I'm learning R.

The thing with Excel is there's a low barrier to entry, but there are a lot of differences between a great spreadsheet and a bad one. Somewhat like a junior vs senior developer, the quality of code/spreadsheet depends on what they know, how well they can troubleshoot, and how good of a system they can imagine (to then replicate as much as possible).

For example, most people are entirely unaware that Tables exist in Excel. When you want the sum of a column, rather than writing =SUM(F7:F39) and cursing when you realize you added 10 more rows and that's why the sum is not updating, you can do =SUM(tbl_Sales[SalePrice]), and when you add 10 rows, the table will automatically expand. Suddenly your formulas are somewhat self-documenting, regardless of which sheet holds tbl_Sales. Crtl+T when you've selected your data, or Insert -> Tables -> Table.

You can also make named ranges, which I would say is an analog between using {a, b, c, tempVar} versus well named variables in normal programming.

You can also trace dependents/precedents, showing arrows for how the data flows throughout the spreadsheet. Formula -> Trace Precedents/Dependents.

Re:Ditching Excel for Python in a legacy industry by listenallyall on Wednesday December 30, 2020 @10:22PM (#25589245)
> structured/ well managed code

Funny comment in a Python discussion. No type enforcement, no requirement for class/object declarations, circular imports/dependencies allowed, threading/gevent/async messes, variable/class scope weakly enforced

Python is great for a lot of things, but the language is not a beacon of well-managed code. Good Python programmers write nice, easy-to-follow code, just as good Excel builders create very nice, easy-to-follow spreadsheets.

Re:Ditching Excel for Python in a legacy industry by quietbritishjim on Thursday December 31, 2020 @07:11AM (#25591943)
I mean... sure? I never said they did. I even specifically said I wasn't disagreeing with your overall point, in the vain hope of avoiding this redundant discussion. I was just correcting one specific inaccuracy.
Re:Ditching Excel for Python in a legacy industry by ogre_codes on Thursday December 31, 2020 @08:30PM (#25599774)
Fair enough, my comment wasn't meant to mock yours.