How to increase the basic knowledge of architecture?

Question

IT education

Hello everyone, please do not scold me for a long post and read to the end if possible. I will be glad to any advice.

The bottom line:
I work in a small city in Russia with 200+ population, in a web studio, the salary for my region is quite high, 50,000 rubles.
I have a stack of HTML, CSS, JS + PHP at work at the level of creating themes, modules for WP, Opencart, Modx, ....other cms.
That is, in fact, the work is rather galleric, but interesting in terms of orders, interesting features, layout. The company only has cms, there are no such "giants as Symfony and Laravel", and in principle the soul does not lie in the back, I like the front and the client side.
There is only one complaint about the work itself - there is no growth, and if there is no growth, the salary does not grow either.
Unfortunately, there are 2 vacancies in the whole city for React and View, PHP as WP and Bitrix, and a couple of vacancies for C # middle + and senior java. + The rest is a studio with a smaller amount of salary (2 times). The student himself (another 1.5 years to study), so the relocation to a large city does not yet shine. I have been trying for a month now to go remote and leave the studio, but the front of the juniors - there are very few vacancies for remote work, more middles are required. Or - I went to 2 interviews, but I didn’t like the fact that the same galley that I have, that is, you won’t get help and questions, problems are also solved through a stack, there’s no one to tell me whether I’m writing shit code or not.

How I'm trying to solve the problem:
At work, for 2 years I raised my skills to a good level, I calmly work with native js + jquery. But he himself, realizing that I was stagnating, sat down tightly for pet projects, took react as a lib\frame, now he is hooked on next. I don’t go into backing much, so for the time being I take services like firebase as a back. I calmly made a couple of projects like a service center with authorization, pagination, filtering, drag-n-drop and other stray things - in general it was difficult, but stack, toaster and google solve all problems.

What doesn't work:
The critical problem is that I don't see the correct architecture. And it's downright unsettling.
Example: I am making a spa for a service center, dividing it into components, into pages. Next, I learn that accessing the api (namely, the creation of logic) directly from the component is not true, for this they create a separate folder and shove the api there dividing it into logical structures, for example, api with a request to clients, api with a request to broken devices, etc. OK. I'm rewriting.

Then I google further, I understand that I don’t rub props through the entire application, for this there is a context, I create a context, wrap the entire application in it, and then take it directly. Again I rewrite "everything" application.

And there are 1000 such moments and 1 search on Google and Stack. Everything is going bit by bit. This is not to mention that I just found out that there are such things as spoilers, writing certain keys to env, and a bunch of other examples. All fragments, and very crumpled.

Question: are there channels on YouTube, or good books that will show how to do the architecture correctly for such examples, and how not to step into the shit code? Explain why it is so and not otherwise?
I’m generally silent about design patterns, about OOP, because I don’t understand how it is applied. Of the patterns, so far I have used only the observer, and then at the mobx level and under it either.

I will be glad to any advice.

Answer 1

And there are 1000 such moments and 1 search on Google and Stack.

In general, the fact that all this you have in practice is a big plus.
After something is done incorrectly and then redone - this means that in memory and in understanding why it is wrong it is better to postpone it than if you read it somewhere and forget it.
Keep doing what you do. Lots of practice, lots of googling. You can watch someone else's code, but here the problem is that in order to understand its meaning, someone else's code does not need to be looked at, but it is necessary to delve into well, and this is the time. Therefore, you need to select 1-2 open source projects and deal with them, from the inside, it will be clear where the architecture is good (and why and for what it was done this way), and where "historically" or "urgently needed to be repaired."

Answer 2

Similar question to which I also answered
Where can I find books or courses on PHP, where application design is given taking into account OOP?
In general, I think that working in a web studio is the best (so far), what happened to me happened in terms of pumping skills, there are a lot of tasks, various ones. Constantly new solutions. And with experience, when you solve similar problems, you begin to see better solutions, how to improve, how not to cheat once again ....... It's
just that some things come with experience ......
Here you understand, there is no practical advice as such, download skills while you can. And remotely to Moscow or somewhere else.
You are probably 20 years old, maybe a little more, you don’t have your own family? Then the advice I would give my twenty-year-old self...
Forget the heifers, forget the parties, educate yourself. Learn English, learn one or two technologies, a framework and strive to reach a salary three times more than now. It will be difficult, difficult to give up girls, parties, but then everything will be justified .....
Then the girls will appear and money, and everything that is needed ......
Sorry for the scatter of thoughts .... I still work now....

Answer 3

I think it's worth trying to look for a solution to your problem in the social and process plane.

At work, for 2 years I raised my skills to a good level, I calmly work with native js + jquery. But he himself, realizing that I was stagnating, sat down tightly for pet projects

And what do people who make decisions in your web studio say about this? If no one is using the tools you think are effective, why don't you be the first?
The advice may be a little harmful, since you are just a beginner in react and in general in development, but it will be more harmful for the web studio, and not for you.

Answer 4

The surest and most correct option is to rock yourself as much as possible for pre-jun. Make a pet project, bring it to mind, go to hh with it and gouge for every vacancy.
The best vacancy would be - a) a product company where the junior is mentoring (code review, help with problems, training, etc.) b) a company where you don’t rush at breakneck speed to close the task at least somehow, if only it works. There are not many such companies on the market, so you will need to look.
In the meantime, unfortunately, the conclusion is this - now they are throwing middle work on the jun, so in a project where a beginner has to do logic like "conditional rendering depending on server data", modal output -> a person writes shit-architecture and the application dies like a moth, so how not extensible.

Answer 5

Try to start going to social services looking for remote jobs in your stack for the middle position. As an option, it’s even better to go to an outstaffing company, where in a couple of years you can go through several different projects and study the processes, the architecture and stack variations, etc. from the inside. At the same time, you can read books, watch videos about architecture and further develop in this direction.
Offline is fading into the background, now many companies have learned online, which generally removes the issue of geography.
In the medium term, download English at least up to B2, then you will also have a foreign outstaff with slightly different rates. :)