Disclaimer. Initially, the article was intended as additional material that would help novice developers. I conceived it when I worked in outsourcing, where they often hired promising guys, but without experience. And everything that would follow in the article had to be explained on the fingers. Therefore, the idea came to collect everything in some kind of auxiliary methodological material, so as not to repeat myself. In the end, it all turned into a report (link at the end), and now into an article.
I wouldn't want this article to be perceived as a "Path from Junior to Senior/Lead" guide. Because, first of all, you need to do well and exceed your main developer tasks. And the advice from the article is auxiliary. You can't get by on them alone. But you can't do without them either.
So, let's imagine a off page seo service newbie who has embarked on the path of a hero from junior to senior or lead, or maybe even to manager. He just completed courses, broke into IT and his hands are already itching to paint buttons , but then he encounters surprises...
Step #0. Interview
Without interviews there will be no work, and without work there will be no career.
During interviews, we usually talk about event-loop, how specificity correlates with cascade, how Reflow and Repaint work. And our interviewers also try to test the junior's soft skills to understand whether he or she is a good fit for the team or not.
Jun prepared well, passed the interview and got an offer. And what will be his first task? That's right - the first task will never be "Move the form"
Step #1: Fix the infrastructure
Something will always go wrong for a newbie in a new project: our VPN won't work, or we won't have access to GitLab or YaTracker. If he was able to start working fully in the first week, that's a success. But what does a junior have to do with it?
It has nothing to do with it. That's why the junior is not lazy (and not afraid) and turns on the "unsubscribe" mode:
writes all necessary formal applications;
writes to the manager that something is not working or something is missing;
records(!) all of this in writing.
Jira, Trello, YaTracker, email and A4 sheets of paper when needed – everything is used.
Some of my colleagues did not use corporate mail, did not make requests, because they considered it unnecessary. It seems they told the manager verbally, he heard. And then, almost the same manager asks six months later, "What were you doing then?" Requests and letters would help here - bribes are smooth - here is a paper, I don't know anything, "the problem is not on our side."