|
|
|||||
 Introducing PTWin32 |
You’re
driving with someone giving directions. You tell them to turn left but they
don’t hear you. They ask, “Did you say turn left?” and you answer,
“Right.” The resulting confusion is due to a bad specification. This
example is easy to understand because it is simple. If you apply the concept to
a PTWin32 user directing us to make modifications to their system, it can get
pretty complex, pretty fast. We
want to make sure that you get what you want and that most of the ramifications
of your request are considered. We do this sort of thing all the time for folks
all over the country so we already know a bunch of the pitfalls. Most
of our users let us influence the specification by making us part of its
development. This way we can both make sure that some unforeseen problems
downstream are avoided. But some users hand us a preconceived set of rules for
modifications. This
is okay if the rules take everything into consideration but usually they
don’t. This is to some extent true for rules and laws of all type everywhere. We
advise you call us to discuss your proposed modification to PTWin32 before you
draft any kind of rules for the way the modification should work. Keep in mind
that rules tend to cut both ways.
|
||||
 |
|||||
