How to effectively develop yourself as a developer?

Question

JavaScript

I recently got a job as a js dev, I want to not just cut routine tasks, and if I’m already lucky with the task, then improve my skills, but I want to develop myself as a developer as efficiently as possible in order to become not only a full-fledged dev, but also a good specialist, what advice can you give June in the development of the developer's skills, and in the development of js itself. you can take a book of 900 pages, stuff yourself with theory, and then if you don’t close it up, it’s no use and it turns out that time wasted, and even if you fix it, then it turns out that the book is old and no one writes like that anymore, I need useful tips for the time spent on which will really be justified.

Answer 1

It will be much easier for you to solve most of the tasks facing you (and it is much easier for others to help you with this) as soon as you stop describing them with general phrases (such as "maximum efficiency" , "full-fledged virgin" , "good specialist" , etc. .P.).
- "My goal for the next 6 months is to grow to the XXX position in the current company." And further:
- "What do I need to do in order to grow to XXX within 6 months in my company?"
With this, you can already turn to people with sufficient competence in helping you with the answer to this question:"In order to become XXX in our company, you need to know THIS and be able to THAT."
- "What do I need in order to know THIS and learn how to do THAT?". You draw up an action plan (break down the necessary steps into months, weeks, days) with deadlines (to check what was planned and achieved, make the necessary adjustments in connection with this, etc.) - and go ahead.
- "... I want to develop myself as efficiently as possible ...". What exactly does it mean (for you) "maximum efficiency" ? By what criteria will you determine whether you are developing effectively or not? Number of books read? The complexity of the tasks to be solved? What exactly?
- "...to become not only a full-fledged virgin ...". What exactly does (for you) "full-fledged virgin" mean ? How will you understand that you have become a "full-fledged virgin" ? Will you achieve a certain position? Will you earn a certain amount of money? What exactly?
Good luck.

Answer 2

hexlet.io

Answer 3

Friend, hello.
I don't know your level of Js, but in any case, better than mine, because I'm just learning it.
For myself, I made such a plan to conquer this language.
1)Head First "Learn JavaScript";
2) learn.javascript.ru ;
3) Good Parts;
4) Secrets of JS ninja;
5) pocket guide js-partially;
6) JS templates;
7) ES6;
8) 68 ways to use js.

Answer 4

I'll put in my five cents.
I'll start as always, probably from afar, sorry.
I had quite a bit of time to develop at home: a child, the remoteness of housing from the place of work, etc.
And now I spent the past three days of the weekend researching some things.
I read almost half of the documentation on Vue, launched hello world on a clojure script, and galloped through Europe through FRP implementations on js, stop at cellx. I spent the whole evening with her.
And only after that I felt that forgotten feeling when you learn something new, broaden your horizons.
Why am I doing all this?
I remembered that before the move, before the child, I "flew" home and studied something new until one or two in the morning. I read books / articles / any sources, and asked myself the questions "What if you do this?", "And if you apply this method?", "And if you call with this parameter?", Etc, and tried to answer all your questions find answers.
And also I constantly wanted to "cut" something. Your website, some small project. Some small plugin. You can go on endlessly..
The most interesting thing is not that I received some interesting finished product - this almost never happened, but that I improved the quality of my skills, learned something new, because sometimes something did not work, I had to google, refactor, use functions, libraries, frameworks that I have never used before. It is this experience that, in my opinion, makes you a valuable developer.
But - as in advertising - and that's not all.
There are also important aspects that make you a good developer:
1. Ability and love to read someone else's code. Read, understand (edit?). The fact is that on any projects, especially those where a large code base was written before you, you will have to understand the code, and, accordingly, reading and editing someone else's code will take about 65-85% of your time.
2. Lack of fear before reading the documentation. Someone runs to watch articles where people write their experience of implementing or, excuse me, "trying" some technology or tool, and misses a huge layer of information that is described in the documentation. A layer that can delay the start of use, but help you to be absolutely in the subject of what and how you are going to work with.
3. The third point is a little related to the second. You need to know English. At a level sufficient to understand this very documentation. And also read articles by foreign developers. After all, almost everything that we learn is done over the hill, and due to the fact that English is an international language, more and more popular libraries / frameworks / tools, or rather documentation for them, exist in English at least.
These are all, I think, more or less objective points
. And so many letters already, sorry.

Answer 5

Only develop. Only experience. Only practice.
Try to work in interesting offices on complex tasks under the supervision of experienced colleagues.

Answer 6

codewars same
framework tutorials for general understanding,

Answer 7

Vanya has a wonderful mailing course on this very topic. How to get out of the encoder in people.
nemytchenko.ru/blog/all/smart-programmer
Free.

Answer 8

Web developer development map

Answer 9

I don’t just want to cut routine tasks, and if I’m already lucky with the task, then improve the skill, but I want to develop myself as a developer as efficiently as possible in order to become not only a full-fledged maid, but also a good specialist

I'll add aRegius answer
full, good - that's all Relatively .. in programming / development these terms are very controversial .. there are cool specialists who solve complex problems who write code not according to PSR (example from PHP), but there are specialists who write good code , but that's where it all ends, because they can't solve problems especially ..
You used the word "routine", which means you already have an understanding of what "routine" / "stagnation" is.
Stagnation is a good concept for a developer.
Stagnation is just the same as performing routine tasks and lack of development in the future.
If the developer understands this, then you just need to look for a new place of work, new tasks that he has not yet dealt with, i.e. to develop further ..
I'll tell you on the example of myself)
When I felt that stagnation was coming, I simply created / activated my resume on headhunter, potential employers sent me test tasks, I understood / solved them, thereby assessing my level and the level of the employer, then, if the task of the employer was interesting to me, I passed interview, clarified the points that were of interest to me, and in case of greater interest, I went to work for him.
Thus, I did what I was interested in, developed as a specialist, as a developer, fought stagnation.
In general, the main thing for me and my development is the absence of stagnation, and a very important point, to be able to feel this very stagnation.
To feel stagnation, you need to constantly think about what you are doing and at what level you are doing it.
If you understand that at the current moment, you are doing everything cool, then you need to look for something new, challenge yourself, and only then will there be growth.
Bottom line: you need to deal with your real assessment and not be afraid to change something.