The steps of an algorithm are reflected by cells that reference cells that reference cells.
I've always thought that every highschooler should be taught how to use Excel properly, it really is a superpower in many contexts.
The steps of an algorithm are reflected by cells that reference cells that reference cells.
I've always thought that every highschooler should be taught how to use Excel properly, it really is a superpower in many contexts.
It's a trap because once you get comfortable in Excel you have a lot of resistance to try anything more productive than Excel. Seen that numerous times with people who work really fast with Excel yet end up very limited as to what they can actually deal with beyond simple problems.
Basically it grew out of the fact that many of these companies are focused on Windows, given the software of the data readers and laboratory robots.
So it is quite common to have Visual Studio licenses around.
A common pattern for the history of many VB packages I found out across the business units, was software that started in Excel, alongside VBA macros, and eventually was ported into VB.
Let's say my volunteer org wants to keep track of events, who volunteered in them, etc. and wants to give an award to the volunteer who gave the most hours. How do you do that in Python? Why would you?
Personally, I'd go to something like haskell or f# though, because of a even better type system IMO.
Altough, for learning it, typescript is probably easier and more applicable in the real world.
Excel has PowerQuery too, which is very nice but you hit the ceiling pretty easy. Knime eats a lot of data down the throat with modest PC, Excel really struggles with large datasets, not matter how you use or tune PowerQuery.
I know here in HN people talk down visual programming, but I've done pretty heavy and complicated stuff with it. It would be way more complicated with pandas.