Where to go next, what design patterns are used today?

Question

JavaScript

Good evening! I'm learning JavaScript, I've written some simple indie games and applications. Now I continue to go deeper. I don't think about frameworks yet. I'm going to write my "big" task manager, or something like that. I have problems with design, code organization. Several questions emerged.
1. What design patterns are used today in the modern standard?
2. How to deal with the architecture of the application, where to start learning?
3. What to read / watch on the subject of OOP?

Answer 1

Learning JavaScript Design Patterns

Answer 2

Patterns are not OOP.
Patterns can also be in OOP.
Patterns today are anti-patterns tomorrow.

Answer 3

Nothing better in OOP, except for the ancient book "Gang of Four", I have not seen. And ECMAScript has nothing to do with it - the principles are the same everywhere. "Modern standard" is a well-forgotten old one. But this is about books. The best way to study patterns and everything else is to participate in a real project, communicate with real people, review code from experienced developers, etc.

Answer 4

If you write application patterns, then most likely you write shit. You must write an application based on tasks.
Knowledge of patterns is necessary only for communication with colleagues, in order to convey a thought in two words, and not in essays.
In order to start developing architecture, you must first understand what it is and understand (and not know) the definition. 99% of programmers do not know this and try to build architects out of themselves.
GOST R 57100-2016 aka https://en.wikipedia.org/wiki/ISO/IEC_42010
It's easy to search in Yandex. Read and comprehend.
After that understand SOLID. It will be difficult and difficult, especially in light of the fact that half of the articles are from people who themselves do not understand SOLID.
Almost every SOLID principle has a clear criterion based on the properties of the code rather than the programmer's assumptions about the scope.
For example, the single responsibility principle says that for each class, the state is described by a set of properties that always change together. If they can be changed separately, then these are two different responsibilities.
But a property is not part of the state unless it is used in class methods for calculations or in expressions. And for example, they just always come back.

Answer 5

Try using popular application frameworks. They actively use patterns and you willy-nilly get to know them, and not theoretically, but quite practically.