How to upgrade to middle frontend?

Question

Career in IT

I know JS would not say that the basics, but a little more. For example, closures, async / await, axios, mvc architecture of simple applications, react

Went to test on junior frontend. They asked me to make a to-do list app. It turned out to be done.

Question. How to upgrade to the middle? Is there an option to dig into theoretical separate knowledge (for example, a function signature, literals) or to pump practical skills? For example, open the source code of react applications and see how it is done, take courses on building react applications.

Can you, please, professionals advise what development strategy to choose?

Answer 1

Did you try to work?

Answer 2

For three years, diligently work in the office until they are promoted to middle.

Answer 3

go to work and make 1000 tasks from the tracker there

Answer 4

The easiest way to upgrade is at work, where they tell you what technologies you need to know and there are people around who can help you learn.
There is little sense in mastering technologies outside of work - it is not yet clear what is really useful in work. The accumulation of knowledge is not as fast as in a team.

Answer 5

I will answer abstractly. Without reference to the front / back,
Middle is just a specialist who can clearly carry out the assigned tasks himself, without sensitive guidance and explicit instructions. Of course, this is a practice, and above all, commercial / paid projects. Those certain professional experiences that will allow you to feel the technology, people, teams, business tasks.
He is also able to make some tactical decisions himself, according to how exactly to do some things. Thus, as soon as you stop asking yourself the question posed in the topic, you are already closer to the middle ;-)
Senior is a logical further development, here a person is already ready to make more serious decisions on the structure (and in many respects the architecture of the project), plans a lot himself, is able to get a problem statement from the product / business and himself form a task and solve it roughly speaking alone. For tasks that are not related to his profile, he will successfully delegate and / or cooperate with other specialists, again, without additional guardianship, but he himself takes responsibility.
Therefore, by the way, many stay in the middle level, not because they are straight oh oh bad specialists, not at all. It’s just that moments with decision-making, active actions with other people, command, and so on are far from suitable for everyone.
BUT, it’s worth noting right away, it’s already been written here above, and I’ll also say it. Many companies use the terms junior/middle/senior at their own discretion, so these are often subjective parameters.
But, it seems to me, what I have described will at least meet most of the requirements of both middle and senior, and maybe even move to a higher gradation for some.
As for specific technological pieces. then the network is full of collections. development paths (google Developer Roadmap and the like), but without practice in real projects, preferably commercial, but many open sources are possible, this means little.

Answer 6

It is better to be a practical junior than a theoretical middle.
Without participation in real projects - in any way. Only in battle will you gain... by working in a team of competent programmers.

Answer 7

To be considered a combat middle, you need to successfully solve 20+ small and medium-sized projects, collect the main rake in practice, develop hundreds of ready-made micro-solutions for all kinds of cases, know and be able to use basic algorithms and data structures, have a good command of the basic API of the language, be able to understand tasks and solve them in accordance with expectations, albeit not ideally.
Any developer is expected to solve more problems than they create. Therefore, they look very closely at the experience, first of all.