2 ms·
Not really. You start from the solution cells and work backwards. It might be easier than reviewing a functional programming language that does the same work.
by jpadkins 14y ago
Not really. You start from the solution cells and work backwards. It might be easier than reviewing a functional programming language that does the same work.
Think about all the accounting and financial decisions that is reviewed in excel. They are vitally important to get correct.
- DanBC 14y agoThe European Spreadsheet Risk Interest Group[1] has a list of spreadsheet errors. (http://www.eusprig.org/horror-stories.htm http://www.eusprig.org/horror-stories.htm) There are lots of errors in accounting and financial spreadsheets. It's vitally important that traders enter the correct numbers when making trades, but 'fat finger errors' happen pretty often. Ray Panko has a lot of useful research about spreadsheets. Part of the problems he identifies are difficulties in auditing and finding errors. [1] (http://www.eusprig.org/ http://www.eusprig.org/) [2] (http://panko.shidler.hawaii.edu/ssr/ http://panko.shidler.hawaii.edu/ssr/) My internet is flaky, and none of the links I find work.
- salman89 14y agoGoing cell by cell in a backwards fashion seems to be a tedious way of checking for errors, and goes against your normal logical flow (forwards).
- rayiner 14y agoIf you're a a programmer in a typical imperative language, sure. If your familiarity is with data flow or functional languages, you work backwards all the time (or rather, you work top down, from the highest level of generality to the lowest level of detail).