Who likes to learn from the scratch the same issues over and over again. Assume, that nobody.
But sometimes we have to do so with design patterns, because that is not the case we have a close contact with every of 23 classic software design patterns.
I don’t remember, who wrote that:”we uses implementation patterns every hour, we uses design patterns much rarely, and we use architectural patterns mostly at the start of the project”.
And when we don’t use some of our knowledge for quite a long period of time, we actually loose this knowledge, and will have to learn it again, when we need it.
I think, that design patterns are worth remembering, because it is not the case, when you’ll have to forget it later, because something new will appear. Software design patterns are core solutions for constantly appearing daily design tasks. And mostly, it doesn’t attached to particular programming language, or framework(but every implementation has its own differences).
