Which set of tools to choose and how to learn them for the web?

Question

JavaScript

While I am in my fourth year at the university (information security), however, in prof. The area doesn't appeal to me at all. I decided it was worth trying my hand at the web, as I have always liked programming as such and enjoyed learning it, and the web seems to be the most interesting area for me. Fortunately, I have another year and a half at the university, when I can still study without much haste.
But while I was looking on the Internet, what is now worth teaching in this case, I realized that I did not understand anything.
So far, I have come to a very logical conclusion that knowledge of html, CSS and SQL is definitely needed (and, in principle, the ability to work with the database), JS is also required for the frontend.
But I want to try myself not only in the frontend, and here the question arises, what is needed for the backend?
Personally, I am now considering Node.js for several reasons:
1) It is essentially JS and you will not need to learn another PL
2) It seems to be popular, including in terms of vacancies
3) It seems to be actively developing and gaining popularity
And so , question. What am I missing? And I feel like I'm missing something.
If we talk about me, then I have:
1) understanding of computer architecture, and knowledge of how the network and data transfer works,
2) knowledge of English at a level sufficient to read those. literature, albeit with some effort
3) Some academic experience with databases and sql queries
4) little programming experience: two very strange semesters of studying C ++ (such that I didn’t understand anything about the pluses) and a couple of months of independent study of python (everything with python is much better for me than with pluses).
PS Yes, I understand that the question looks like it's easy to google, but as it turns out, it's not that easy. Especially given the speed of technology development on the web.

Answer 1

For a young Padawan to speak fluently in the main web programming languages ​​-
js first, then css and html
Flanagan's tutorial must be completely digested
and php a little to begin with - only the basic server functions for working with folders and files,
or better - learn api node.js - and make a server on js
js - a very simple language, nowhere easier, Lisp in the skin of C
and the most cross-platform - for beginners, do
not forget the KISS principle - we appreciate minimalism-simplicity-lightness
without other people's frameworks and libraries you will get maximum js performance - in 3 -5 times less than in C
in the process of studying, you need to write your own simple client-server application -
a blog, a drawing tool, a text editor, etc...
the main thing - without using someone else's code - without libraries, frameworks and ready-made databases,
you must be able to independently create, process, save the data you need
thick client - skinny server
offline and mobile first
bike first
, after that you will inevitably gain enlightenment
and become a real engineer as a webmaster- a programmer
or even a Jedi or a ninja, if the Force stays with you for
three to five years, for this you need to gnaw on granite
and you can sell your mobile applications in an appstore, for example
, there is another way - the dark side of programming:
working on someone else's ready-made standard template-framework is an
endless cycle in samsara of capitalist industry
communication with morons, psychopaths, crooks, lazy people, etc.
office or freelance suffering
easy replaceability of a programmer
eternal reworking of someone else's code
inability to do the necessary functionality on their own
constant googling of ready-made solutions
depression and despondency
//and the laziest become layout designers-underprogrammers))
programmers are divided into two types:
1) engineers - those who can write a template for themselves or for others
2) fitters and carders-winders - those who work within the framework of a ready-made template
- both types are needed, it all depends on your abilities and talents

Answer 2

Learn JS syntax if you want, but read smart architecture books. Code culture in JS is extremely low right now. And Node.js is just a platform for executing javascript code on the server. There is nothing to learn there, I opened api, but I did it. But first, of course, you need to learn the syntax of any language that supports the paradigm that interests you, otherwise architecture books will be completely incomprehensible. Now the OOP dominates. Therefore, you can take any that you like JS, Python, PHP, Ruby. It doesn't matter, they all know how to OOP, in JS they use prototype-based, but this is just one of the styles of object-oriented programming, the essence does not change. Well, in JS, oop is a bit hacky, but there are languages ​​\u200b\u200bthat compile to JS designed to correct this misunderstanding, such as TypeScript.

Answer 3

Fortunately, I have another year and a half at the university, when I can still study without much haste.

Guy, forget about the fact that you have time, treat yourself like you're already late, then there will be no problems with motivation. If you are interested in Node.js - then here is my question to which I myself unconsciously wrote a good answer: How to learn Node.js?
I hope that in time you will have a wind in your head like “Well, you have to choose the direction very carefully so as not to make a mistake”, and you will soon start doing what you like by choosing the right tools for it. Good luck.

Answer 4

On the 4th year, you already need to have 3+ years of work experience
Until you try everything, you won’t choose what you like
No one will choose for you
On the background, you can use almost any existing Japanese

Answer 5

If everything is already much better with Python, you can continue it. There are purely Python vacancies, and there it is quite possible to grow and participate in the creation of good projects. And if there is not enough - right there, in the team, you can find someone who will help you figure out what you like best. After all, then it will be possible to see in practice the work of front-end workers and back-end workers, and understand whether you want to do this.
As for me, front-end workers are more for a creative mindset, who likes to make beautiful things, to create. And the backend is for an analytical mindset, there is no need for creativity there.
Depending on your character warehouse, according to the results, one or the other will pin. I do not advise you to choose for a long time, to aim, and then in practice - to suffer, and eventually become ... a photographer.