# from Fergal Daly
# on Friday 23 January 2009 02:07:
>The point is that you want to declare your intention independently
>from taking the action. If you declare the plan alongside performing
>it, then your planning becomes subject to bugs.
I'm sure that for every reason someone can cite about needing a
statically coded numeric plan, I can point out in detail a method of
refactoring such that the plan becomes a number which is at least
closer to the data involved. If you generate the list of things to
check, code in a test that this list is 7.
You simply need to assert what you mean to assert *where* you mean to
assert it. That might be a static number in one place while in another
place you might simply check for matched sets and so on.
--Eric
--
"Matter will be damaged in direct proportion to its value."
--Murphy's Constant
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
