How to be a good junior?

Question

IT education

Hello seniors, what do you value in junior programmers ?
Now I work as a junior, I try to take on as much work as possible,
I try to solve problems not only in one language, I delve into writing high-quality architecture + TDD, I solve
problems on codewars (in my spare time)

Answer 1

1. Adequacy and independence.
More details: The ability to understand the essence of the task in order to complete it. Independently solve problems - this word includes not only the fact that a problem has arisen - it has been solved. And the ability to solve problems that you cannot solve. That is, to organize a solution to the problem. Account blocked? Find out, call, kick, so that they unlock it faster. You do not know how to solve some technical problem - to get through to the curator. Do not sit and wait for three days until he remembers your problem, but check it regularly. Busy curator - go to another. You do not have time to decide on time - come to the curator in advance, and not an hour before the end of the deadline.
Basically, don't run after you.
2. The ability to ask the right questions.
First google, then ask a question for clarification. Ideally, ask questions to which the answer will be "yes" or "no", but I exaggerate this. Do not be afraid to ask things that you don’t understand at all, but here you don’t need to expect that everyone will chew - you should ask a question in order to understand where to dig. Sometimes it’s enough to know a couple of keywords that you can google for.
3. Desire to learn.
Do not be afraid to study too much, because "I won't need it." Ability to google for keywords. Do not be lazy to study how something works in order to understand why it happens. Understanding the principles of work greatly increases intuition.

Answer 2

Sometimes, after attending a certain number of interviews, one gets the feeling that, in the understanding of the employer, a junior is the same middle, only they will pay him like a junior))
In some cases, a junior can mean an almost completed middle, but with insufficient work experience (no experience) , who is given such a kind of probationary year, after which they are "initiated" into the middles.

Answer 3

A good June is called a middle. A good middle is called a senior. A good senior does not classify a programmer into juniors, middles and seniors.
If you want a promotion, go to your boss and learn from them how to be good. If you want self-development, then why do you need to be a junior, even a good one?