The thing I have found that people tend towards extremes, they believe that you have to test for everything or they test nothing.
The people who test everything believe that they can prevent anything bad from happening by writing enough documentation or produce X no. of tests or X amount of code coverage.
The problem is that testing and documentation becomes the objective. People who delve deeply into the details they lock themselves to a particular process/solution. You cannot change your design because it would involve changing your documentation and your tests and that requires a lot of effort.
The other group believe they are infallible and that testing and documentation is extraneous, unimportant and don't bother with it.
The problem is that people make mistakes, and these mistakes are found only when it is sent out to the customer.
It takes some thought and work to find a good middle ground, but most places don't really work to do that.
In reply to Re: "Practices and Principles" to death
by Herkum
in thread "Practices and Principles" to death
by ack
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |