When to learn design patterns?

Question

OOP

Hello, I'm currently in the beginner stage and working as a private for [company name]. I am engaged in the fact that I write mainly client code, i.e. I use api clients, write bots, and projects are usually small (in general, backend). Does it make sense for me to learn design patterns? If yes, why? If not, how do you know when the time has come? Well, what to look for before teaching them? (clean code, refactoring, language mechanics, frameworks)

PS I use frameworks (laravel), I understand that many patterns are used there, but their ignorance does not prevent me from writing on it yet.

Answer 1

When you become middle, and maybe later. Patterns are not for juniors.
Patterns are mostly used in OOP, if you don't use it, it's worth understanding why. If you do not know - study, and there are already patterns. If there is simply nowhere, then hammer it in for now.

Answer 2

I allow you to read the book https://ru.wikipedia.org/wiki/Design_Patterns
In addition, I do not forbid using them and searching in the code

Answer 3

I use frameworks (laravel), I understand that many patterns are used there, but their ignorance of writing on it does not bother me yet.

The trick is that you are already using the patterns, even though you don't know their names.
Read a review article like this first , it won't take long. If most of it is already clear, then it may be worth reading a book and fixing the material. And if everything is complicated, difficult, incomprehensible, then postpone this topic for now.

Answer 4

when you go to an interview to "sparkle with knowledge"
I regularly go to interviews to "lift my tone" - everyone there constantly asks me about patterns. I had to read about them - I did not endure anything new for myself. someone (who knows, but I don’t bother memorizing) described them quite ordinary programming techniques