An anti-pattern is devious and insidious and adds more trouble than it removes. In the old days, we used to just call these bad ideas. The new name is much more diplomatic.
The Architecture-As-Requirements anti-pattern refers to situations where a prominent and influential member of the design team has a pet technology or product and absolutely wants to use it in the project—even when there is no clear evidence of its usefulness and applicability in the customer's context.
The Test-By-Release anti-pattern refers to releasing a software product without paying much attention to all those boring and time-consuming chores related to unit and integration testing. Are users the final recipients of the product? Great, let's give them the last word on whether the software works or not.
No comments:
Post a Comment