|
|
|
|
In article am writes:
Actually, there are a lot of us programmers who have learned that strictly
following processes that divide up refactoring and improvement stages are well
worth doing, and we do it pretty rigorously.
That's a good thing if you're working for customers who can afford it.
But it's one of the things that makes software more expensive than
many people believe it should be.
Unfortunately, fully automated, complete, repeatable testing is, AFAIK, not
possible with a studio wiring plan. it would be nice if it were.
It's not automated, but you should test every path, and every jack. It
takes time, but it can (and should) be done, at least once, when you
install it. Unlike software, wires break and jacks don't always make
good contact, so even if you know it used to work, sometimes it
breaks.
Ah, but it's not the same jack, and was the module properly normalled? Is it
the same wire, or did I use a different cord because it needed to be longer?
Well, you're using a jack that used to work (but you may have miswired
it when you make the change). And if you change the cable, then you've
made two changes without testing.
--
I'm really Mike Rivers )
However, until the spam goes away or Hell freezes over,
lots of IP addresses are blocked from this system. If
you e-mail me and it bounces, use your secret decoder ring
and reach me he double-m-eleven-double-zero at yahoo
|