I think a lot of the issue with Excel is the developers, often, look down upon it. This is too bad as it doesn't help those using it to solve real world problems and it often leads to them not seeking help. Then we end up with the billion dollar London Whale's.
I don’t look down upon excel I look down upon development practices inherent to excel.
No proper way to collaborate with version control. No real change control either - Joe can have version 1.4 Bob still 1.0 - version from Bob making loses for the company.
No real way to debug like getting to know where cell is used is impossible.
That said excel is powerful and I also use it for personal stuff or stuff only I need to calculate.
When I have more than 5 people using and changing the same excel all is lost - maybe office 365 helps with collaboration but it still needs a bit more features.
That said excel is awesome on its own - single spreadsheet with complex calculation used by more than 5 people is recipe for a disaster.
I use it for quick table to code codegen often. But it wasnt about you personally just the comment’s people make about it. With onedrive people do get a sort of versioning, albeit very crude, too. But your right, the practices are bad and part of it is people are not having conversations about best practices. Also, the cost of development being what it is and people’s incentives, Excel fits into that just get it done and deal with it later spot. I know in my org it was a minimum of 50k to get a dev shop, internal, to do a project. This was years ago too. Too many big fish for them to work on. So the small groups went with what they could use. Also, it is on all machines.
