A
A
Alexander Tarkovsky2017-05-07 23:31:02
JavaScript
Alexander Tarkovsky, 2017-05-07 23:31:02

What Should a Middle Node.js Developer Know?

Good day, colleagues.
I would like to know what a middle node needs for a node.js developer position and how to grow up to it.
Now I am in some kind of stagnation: I spent the last couple of months closely studying and using ES6 in conjunction with CoffeeScript, wrote many full-fledged APIs (OAuth + Postgre), started using asynchrony not everywhere, but where necessary. After rethinking everything and taking a break from programming for a week, I realized that I didn’t know where to go on my way to middle.
Now, the crux of the matter:
1. Are there any tips for advancing your skills towards building REST applications?
2 Can there be an option for employment immediately for a midlle position, taking into account completed projects intop company?
2-1 If "yes" : does work in your own team usually count as experience (where you make applications "for the soul" and hone your skills with friends, in my case: 2 Python programmers, 1 Java, 1 Node.js)
2 -2 If "no" : is it worth it in this case to advertise yourself at various events (hackathons, conferences, etc.)
3 What skills, besides a solid knowledge of node.js and basic modules / frameworks, would be desirable to master at this level? (Knowledge of TypeScript, some specific technologies or something like that)
4 If you were a middle in this field, information about the technologies / services that you used and which were most useful would be invaluable.
4-1 What do you regret most about not knowing in this position?
I would be grateful for any advice or hint.

Answer the question

In order to leave comments, you need to log in

2 answer(s)
A
Alexander Tarkovsky, 2018-05-15
@maximtark

Returning almost 2 years later to my own question, I would like to answer the questions that I myself asked. Maybe my findings will be useful to someone. :)
1 Yes. A lot of them. But they are useless without understanding(!) REST at the abstraction level. Literally a couple of days after this question, I got into the office, where for a year I was engaged only in it. I stepped on a rake from the fact that I was very attached to the capabilities of the platform (Node.js) and looked back at the documentation. Trying to do it "right" I got a lot of bumps, and then I just started doing it for people. nobody appreciates correctness... Especially mobile developers(¯\_(ツ)_/¯). Conclusion: the question is incorrect.
2 Yes. And how much in a good office - it depends on the case / mood / something else. Well, from the level of developers who apply for the desired position. It is difficult to find a "top" (the words of a familiar HR) developer, it takes a long time and is expensive. So you can always fill the weekdays of recruiters with your humble persona. Passing interviews and selling yourself is also a must.
2-1 Keyword "experience". You need to convince a potential employer that a pet project (or a whole zoo of them) is potentially viable. Unfortunately, no one appreciated my vector layout of the Earth, the position of which depends on the time zone / current time, around which all known satellites from a third-party API fly (well, cool! They were also clickable!). But they appreciated the pathetic semblance of a simple blog constructor. One of the top 3 biggest disappointments of my life. :(
2-2 Yes. Definitely. Definitely come, listen and speak only if you have something to say.
3 Well, there is generally an epic. For myself, I singled out only one useful skill. "Look for a suitable screwdriver to unscrew the door. Not a door to unscrew it with your own screwdriver." There is no silver bullet. Conclusion: the question is incorrect.
upd: As a spoiler - I still had to learn TypeScript, CoffeeScript was never useful (although it was my main).
4 Only google.com, docks and a cold heart, which is ready at any moment to digest indignation from immersion in the source code. Well, sometimes you can peep in Open Source.
4-1 I didn't know that in Open Source I could also be taught to smoke/swear/write bad code (underline as appropriate). And I regret it very much.
Outcome. I would really like to give detailed answers without any water. I cant. To my great regret, 2 years ago I still did not know how to ask the right questions.
"Senior, Senior, solid Senior... Hipsters! Call yourself tamers of typing! Damn it, JS Generalissimos have bred! They have put titles on themselves! Who will work? Not a department, but a bunch of aristocrats, undefined for me in the workplace.."
© Tech Lead Misha is indignant in the smoking room. 2016

C
Coder321, 2017-05-09
@Coder321

Well, sockets, I think this is one of the main things you need to know, plus a mong is also very helpful.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question