RE: Restrict ability to alter variables in debugger on production

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

> From: John Earl
> 
> That's one way to look at it - and it makes sense, but it misses
another
> important point (and I'll take my security hat off here - because it's
> not a "security" issue)
> 
> If all you test with is production data, then you are doing what I
like
> to call an "endurance" test rather than a "function" test.

I never said that.  I completely agree with the "big, bad, ugly test
database" concept.  In fact, I advise people to have refreshable test
databases as part of their test plan.

I just said that in the real world of application development there
exists a class of problems which never seem to be identified except in
production.  In fact, I'd be willing to make it a Law, akin to the
Murphy laws:

Pluta's Law of Infinite Conditions: The number of data conditions in
production is always greater than the number of conditions tested.

Joe