When should developers read and learn about design patterns?

Question

I want to know when developers should read and learn about design patterns? Is he junior, senior or above senior?

This question is very vague for me.

Answer 1

In the beginning, you must have passive knowledge of design patterns. That is, you should be aware of the most common design patterns that they exist, but you should not try to actively use them. Since most design patterns are related to class design, you must understand the classes and structure of the program before learning design patterns.

, , . , . , , .

Answer 2

, , - .

Head First Design Patterns - .

Answer 3

, , . , senoirs , , , , , .

, , Head First Design Patterns, , , .

Model-View-ViewModel (MVVM) , .NET 4.0 .

Answer 4

. , , . , , , .

If it depended on me, I would prefer people to write a lot of code. Just do it. Write the code. Make a mess, feel the pain, fix it. Design samples are convenient later when you need a vocabulary to express solutions to teammates.

In addition, I think that Refactoring should be on every table in front of design templates. This is much more pragmatic.

Only me, however.