How to drag a middle developer to the front-end without spraying?

Question

css

Hello everyone, I'm a junior front-end, relatively recently joined the ranks of developers and, like many of us, I'm interested in developing both my skills and moving up the career ladder.
Logical and harmonious growth and the next step is the growth to the middle.
In this regard, the question arose: what do you need to know for the level of a middle developer, what technologies, how many years of experience, what do you need to be able to do?
What is the must-have skill checklist? And what technologies can be skipped and not sprayed on them, at least on this segment of the path.
Since there is a lot of interesting things, but you can’t keep up with everything.
I understand that the requirements differ from company to company, but what is the average standard in the market?

Answer 1

The difference between junior, middle and senior is not in the number of terrible words they recognize, but in the level of setting tasks.
the task is set for the jun - well, they washed down the class / function for me, the
middle - washed down the application for me, the
seigneur or the team leader - here are the requirements for you, here are the documents for the process, here is the team. saw.
exaggerated somehow so
ps
Yes, the answer to the question. work and take on more responsibility

Answer 2

Must have:
- HTML5/CSS3 - at least perfect knowledge
- JavaScript, including ECMAScript 6-7
- In the order of things - Bootstrap + Jquery
- Grunt/Gulp, Bower
- Knowledge of at least one framework. Now more or less running ones are Angular.js and Backbone
- Knowledge of the Git version control system. Ability to work with GitHub / BitBucket
- Experience from 2 years
As a plus:
- Knowledge of Canvas, SVG, ability to write games
- Knowledge of design patterns
- Ability to cover code with tests
This is a generalized set of skills for the market at the moment.

Answer 3

Basically, I'm a junior in terms of programming experience. But from management experience I can say for sure - all these abbreviations are complete garbage. Abbreviations are not important, what is important is the ability to quickly assimilate them. Moreover, I will say that the ability to quickly switch to other frameworks, other development environments, other languages ​​is important. These are nothing more than tools. And for this you need to deeply understand exactly the basics of programming, patterns, algorithms, that's all. Only one way can help in mastering this: fuck (sorry for the mat, but this is the most appropriate word).

Answer 4

one.
Use a profiler. In other words, your leader. Always keep your finger on the pulse. If it’s customary for you to take tasks from the bug tracker, then you can, in addition, agree with the manager on the following practice:
“I ask you to tell me weekly one thing from among the last week because of which you would fire me and one more thing from among the past for the week for which you would write out the bonus. Write down the answers, look after each new feedback from the manager and you will be in the trend, what you need in fact, what the hell you don’t need to do! At the same time, you will be aware of whether the team needs it or is it about to be kicked? That is, you will always know how much you really need.
2.
Having the facts on hand about the real need for the team and what the leader expects and those tasks in the bug tracker, you can put another question to the team: "What pain do we most often experience, but somehow everyone doesn't get it?" and solving it you will need team
1 and 2 give knowledge and career

Answer 5

1. stop using slang
   So from the "middles" you will immediately go to the "seniors". I have friends who have done just that. By the way, it's fast, the question is about weeks.