Design patterns

[Maejie]

I find it that while coding I don't know whether I am using a pattern or not. Before you start out your design, do you need to reference patterns to see if any fits your current idea or you already memorize all patterns inadvance ?
My case, I can't remember all of them, patterns in the same category tends to share some features. DO you have a tip method as a useful way to actually grasp them all better and faster ?
Thank you..

[Maejie]

I think it's funny of me to read something that I don't implement on. Should I quit ?

[alliancetekinc]

I am clueless..

[ahoodin]

O'reilly Head First Design patterns actually implements many design patterns.

Actually alot of them are also documented/implemented in the FAQ on design patterns on this
website.

[blaurent]

Experience comes with time I guess...

If you have a given problem just attack it the way you would attack any other problem. If afterwards you see patterns in what you have coded you should then move onto applying the pattern. This way you see the benefit of the pattern compared to what you came up with.

I think that's the best way to learn when to apply patterns. Also if you go this way it won't take you long to see patterns BEFORE actually moving into designing the software.

Hope this helped

Laurent.