What is Antipattern?
Antipattern is any activity that repeats itself, even though it is counterproductive. Although the term has emerged and has gained extended use in the field of computer programming, it may apply to any form of routine behavior. Identification and description of antipatterns can improve overall rationality by imitating common mistakes in thinking. In this sense, antipattern has general rationality because deception is a deductive logic.
For a dose of code or a set of behavior that forms antipattern, must occur repeatedly. For some observer, it must also be contrasted with a familiar pattern that would almost certainly work better. Insulated errors cannot be antipatters, nor is failed attempts to solve a problem for which there is no solution yet. This definition still leaves space for a large range of defective processes.
There are many different types of antipattern in the original software design category. Some include proceedings of user reactions. "InterfaceBloat "and" Preeping Featuritis " - almost all antipatters were given by cute names - referring to a user interface program so complicated that it becomes unmanageable.
other antipatters include typical programming errors. They rely on existing material instead of adapting their program code they are currently developing. "God's class" is a set of objects within a program that has become too strong; The whole thing is vulnerable because everything relies on these elements.
Many antipatterns have also been identified in the business world, especially as a context for software development. "Specify anything" and "Vietnam War" involves the failure of clarity in the instructions of the management of their employees. “We are idiots” includes the assumption that customers and not forGramators must make any decision on how a specific item is determined.
other antipatterns can apply to many types of organizational sociology. "Groupthink" takes place whenever a set of people is able to maintain collective deception by isolating themselves before the external entry. The "death march" occurs when anyone working on a specific project knows that failure is inevitable, but this information cannot communicate this information. "If it is not broken, do not work" is a piece of conventional wisdom that can be antipattern in contexts where the eventual schedule would be unacceptable.