No, you don't. If you write them yourselves (which is in most but all cases the wrong approach, what with the Java libraries and the C++ STL), you use templates or generics, as appropriate, to define reusable ones.
In many cases, proper patterns are reusable--and in many cases for good programmers, design patterns occur automatically just because they're a logical way to do something. I don't set out to create flyweight objects, they're the simplest way to achieve my goal. I don't write a thread pool just to create a thread pool, I write a thread pool because it makes sense.
Even in 2002, this was the case. I don't get the feeling that the author of these slides knew either well enough to make the claims he made.
.
The Gang-of-Four idea is to discover existing patterns of software development / Then program people to implement them habitually
Er...no. The book Design Patterns is descriptive, not prescriptive. Is that so hard to get?
.
I am by no means a C++ fan, or even really a GoF fan, but this post is slagging it just to slag it. If you want to slag it after you understand it, by all means (and I have perturbed a great many electrons in doing so, myself), but it doesn't sound like the author does, at all.