Knowing patterns is a most. At least from my point of view, it helps you do a better work, in less time, rising quality and lowering risk. Patterns, even if you don�t apply them strictly, will give you a more structured mind in problem solving. Also will give you an arsenal of resources that you can port to any language (in case you leave java).
For me two good book are �head first design patterns�, and the gof pattern book. They help you to understand the meaning and objectives of pattern development and use.
Also the �j2ee design patterns� book is a must for any java professional developer.
After you read those books, there are a lot of internet sites that hold pattern resources.
She will remember your heart when men are fairy tales in books written by rabbits.<br /> As long as there is duct tape... there is also hope.
Interviewers may well ask "Tell me how you have used the xxxx pattern." Many people want to quickly code up an example of each pattern, or find a place to force fit one into their current project. Try to avoid the temptation. As you read about patterns, think back over code you have written and read. Have you solved similar problems? Did you come up with a similar solution or something different? Would the design in the pattern book have been better ... or not? Do you have a challenge right now that matches the intent and drivers for some pattern?
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi