A very important part of the software development process is service or component internal design and implementation. Design Patterns (Gamma et al., 1995) provide list of the common patterns used in the object-oriented software design process. The primary goal of the Design Patterns is to reuse good practice in the design of new developed components or applications. Another important reason of using Design Patterns is improving common application design understanding and reducing communication overhead by reusing the same generic names for implemented solution. Patterns are designed to capture best practice in a specific domain. A pattern is supposed to present a problem and a solution that is supported by an example. It is always worth to listen to an expert advice, but keep in mind that common sense should decide about particular implementation, even in case when are used already proven Design Patterns. Critical view and frequent and well designed testing would give an answer about design validity and a quality. Design Patterns are templates and cannot be blindly copied. Each design pattern records design idea and shall be adapted to particular implementation. Using time to research and analyze existing solutions is recommendation supported by large number of experts and authorities and fits very well in the pattern basic philosophy; reuse solution that you know has been successfully implemented in the past. Sections 2 and 3 are dedicated to the Design Patterns history and theory as well as literature survey. Section 4 contains General discussion and critical view and pointing to the very important warning that Design Patterns are not silver bullet. Section 5 is about Anti-patterns .Section 6 contains examples. The examples are based on the Abstract Factory design pattern and gradually demonstrate how this pattern is built and changed. The title of this paper is “Design Patterns past and future”. Design patterns past is tightly coupled to patterns future. The past offers collection of available patterns. The future is using it as template and adapting it to the new context. The future is adding adapted patterns to existing collection and new patterns discovered by solution analyses.