Just as design patterns provide a way to communicate concisely about desired software practices, antipatterns provide the equivalent advantages for communicating undesirable practices.

An antipattern is a classified bad design; in other words, it is the opposite of a design pattern that suggests good design. Antipatterns present bad solutions in a manner that makes it easy for concerned persons to understand the underlying problems and their consequences.

For example, using a Singleton object might be appropriate in a single-application server environment, but it can actually create issues if not handled properly in a clustered-application server environment. In contrast to a positive design pattern, antipatterns elicit a negative solution or legacy approach (a yesteryear’s solution might be an antipattern in today’s world) that could be the result of a team member’s lack of sufficient information or bad judgment in approaching the design or solving an issue.
Common Antipatterns: design, development, and architecture antipatterns.

Read the rest of this entry »

If a problem occurs over and over again, a solution to that problem has been used effectively. That solution is described as a pattern. The design patterns are language-independent strategies for solving common object-oriented design problems.

There are 23 well-known design patterns, as an Object-Oriented Programmer we should known about these patterns. The authors divided these patterns into three types creational, structural and behavioral.

• Creational patterns are ones that create objects for you, rather than
  having you instantiate objects directly. This gives your program more
  flexibility in deciding which objects need to be created for a given case.
• Structural patterns help you compose groups of objects into larger
  structures, such as complex user interfaces or accounting data.
• Behavioral patterns help you define the communication between objects
  in your system and how the flow is controlled in a complex program.