Some domains are born and some are made uglier by bad specifications
Example: If the age limit for a job's eligibility is not defined clearly in the specifications document, it results in an ugly domain
Each and every simplification of ugly domains by the programmers can be either good or bad
When searching for nice solutions, the programmers will 'simplify' the essential complexity out of existence
Testers in search of brilliant insights will be blind to essential complexity and therefore miss important cases
If the ugliness is because of the bad specifications and the simplification made by the programmer has no harm, then the programmer has made ugly into good
But if the domains complexity is essential (Example: The income tax code), such 'simplifications' constitute bugs
The non-linear boundaries are so scare in ordinary programming that the information on how programmers might "correct" such boundaries when they are essential is not at all at hand
Post a Comment
Post a Comment