One day, a colleague asked a company chat to recommend courses. He wrote that applications and videos on YouTube are not suitable - you need a supervising teacher to "kick" from deadline to deadline. According to the developer, it is control and kicks that most motivate him to absorb new information. There were few recommendations in the thread. It seems that something went wrong in the request. Let's figure it out.
New tools and frameworks are constantly emerging, libraries are being replenished - a colleague from the first paragraph, like many other developers, has a feeling that you need to learn constantly. And along with him - many questions. What exactly to learn? How not to waste time on what will soon become unnecessary? How to learn in such a way as to really pump a skill, and not touch it tangentially? How not to burn out in the first week, but practice regularly?
Only we can manage this process: we are constantly looking for new things, choosing courses and schools, motivating ourselves to start and go through them to the end - no one else knows what exactly we need. All this is very difficult, and there is very little time for study due to work tasks. Therefore, I want to compensate for this lack of efficiency. Together with the developers, we tried to figure out how to achieve this.
Step 1. Assess yourself
To begin with, it is worth assessing your knowledge and skills, your position on the scale of competence. Sometimes it can be difficult to understand whether you are a good developer or not, what can be improved and what gaps prevent you from moving to the next level.
— . , , . .
. , . .
« — . — . , ».
, , .
2.
, . — . — , . , , , . , , — .
( !) — , , . . : , , .
« . , - , . , , : , . , — ».
3.
. , :
« . . - , , -».
« : , , . , ».
4.1.
— . , , YouTube . , — .
, , .
30 , . . , — , .
, .
4.2. . ?
, — . ? Nature. - ( ). , .
, - , - — . : , . — .
, - . ?