Developer grade?

Question

Programming

I understand that there were many such questions. But I'm at a crossroads.
I've been working as a .net programmer for half a year now. But what confuses me is that sometimes I don’t understand what I’m doing and why it works (the reason for this is probably the fact that I came to work almost zero and immediately a bunch of new things hit me. I didn’t have time to figure everything out closer). I heard about the graduation of programmers for junior, midle, senior.
Reading books, taking online courses like "programming for beginners" will be boring for me (although I might learn something new).
The essence of the question: what you need to know and what books, resources help you decide that you are no longer a junior, but a real midle!
PS question tags, these are all things I deal with almost every day. in principle, in this I want to be more legible

Answer 1

To decide, you don't need resources or books, it's enough to say to yourself - I'm a Senior!
But why is all this necessary? Employers do not need your regalia, but the ability to solve the tasks assigned to you. If you are three times Senior, but if you cannot solve the problem of the employer, you will be fired.

Answer 2

Relax. A typical junior is 2 years of professional experience.
It is too early for you to be afraid that you are zero. For half a year, it's normal that you are zero.

Answer 3

Here , in my deep conviction, an exhaustive answer to your question is given.
The original is here .

Answer 4

Depends on tasks.
The senior is given a task - he does it well and quickly (clearly giving out deadlines), even if he has never done this before.
Middle is given a task - he does it somehow, sometimes even on time, especially if he had some experience in a similar or related task.
Junior is given a task - he fails it. The senior or lead decomposes the task for him, suggests algorithms, and points to examples. June finally does it somehow.
In fact, by joining a new team or trying new technology, we become juniors (even if we are mega seniors in other areas). Then we rise to the middle. And, finally, we grow into a senior.
The whole question is in the time of a qualitative leap. If a programmer knows how to understand the processes that take place in a system / business related to the system... Then he very quickly enriches his toolkit, understands the structure of the project and easily becomes a senior. If this is not given, if you see only a branch in the forest, then it will be difficult to reach the middle.
So the whole question is whether you want to develop (go beyond your tasks) and whether you put any effort into it.

Answer 5

sometimes I don't understand what I'm doing and why it works

You are doing something, and that's good. The rest with time
Everyone heard about it, if only someone would standardize it, but no. Most likely, everything looks like this:
0% started learning
somewhere here junior turns into midle
50% half way to guru
somewhere here midle turns into senior
100% guru (unattainable mark)
It's like with a butterfly, is it possible to determine the moment when She's no longer a caterpillar, she's like a butterfly.

Answer 6

How to determine your level of programming?