That was an interesting debate about using formatting info in functions we had the other day. Clearly both sides have valid views and to a large extent it comes down to what you are doing.
Building a complex mission critical system that has to withstand 3-5 years of hamfisted use is quite different from quickly needing to clean up some data to get an estimate out before a pressing deadline (Barclays I’m thinking of you).
In VB.net you have the option to use strict, indeed in VBA we can choose to not use Option Explicit for quick hacking around or turn it on for stuff thats a bit more involved or when more rigour is required. In VS too you can set the level of warnings.
Maybe we need this ‘mode’ functionality in the grid?
Hacking around mode: anything goes, mega formulas, 60 levels of nested ifs, functions depending on formats, scattered dependency trees, functions with side effects in other cells?, perhaps even access the the command table from UDFs? etc etc. multi million rows?
Production mode: much more rigid ‘best practice’ style, perhaps with the option to bypass a rule. lets say no more than 3 levels of nesting, but as a dev you can use your professional judgement.
Then when ever a workbook opens, instead of ‘Active content has been disabled’ it could say, this workbook conforms to Production mode guidance, or not.
What do you think?
What sort of things would you put in each category?
If this were an add-in would you contribute code? would you buy it?