I want to know when should developers read and learn about design patterns? Is it in junior, senior, or beyond senior level?
This question is very fuzzy one for me.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I want to know when should developers read and learn about design patterns? Is it in junior, senior, or beyond senior level?
This question is very fuzzy one for me.
Early on, you should have a passive knowledge of design patterns. That is, you should know about the most common design patterns that they exist, but you should not try to use them actively. Since most design patterns have to do with class design, you should have a comprehension of classes and program structure before you learn design patterns.
The danger when learning design pattern is that you want to use them actively, even if they are not the right tool for the job. If all you have is a hammer, everything looks like a nail. Postpone the usage of design patterns until you hit a problem which you recognize from a design pattern.