Disclaimer: By no means do I want to say that this is the way to learn. But behind 13 years of experience and more than one year of activity in communities, so the reasoning will not be empty. But if you have already become a programmer, most likely you will not be interested in this publication.
A little bit about yourself
I'll say right away: I'm the wrong programmer. I have no education other than school, and I started programming at the age of 25. I don't even have a clear understanding of what I am programming correctly and what is not. Despite this, I have been programming for over 13 years. I am still not very good at various mathematical formulas, etc., but in general I manage to create software products (and, by the way, I earn quite a lot). So I may not teach correctly, but always with an emphasis on starting to make money soon.
Reasoning about the essence of programming
Probably, we need to come up with some other term here to replace "programming". In any case, I can hardly teach programming. But, as it seems to me, you just need to understand the goals. We remember the classic "do you check out or go?"
Most often I see the following picture: on the one hand, everyone says that becoming a programmer is a very difficult task that requires a lot of time and only a few programmers come out of a huge number of applicants, and on the other hand, there is a wild shortage and everyone shouts "we don't have enough programmers!" And here is another paradox: few people generally understand by what criteria to evaluate programmers (that this is a programmer in general). I think that the problem here is that a system for the correct setting of tasks has not yet been developed. Whatever project you look at - you need some fantastic character who can do everything you need. But that doesn't happen. Now, even within the framework of JavaScript alone, so many technologies have spawned, so many approaches, that no matter what project you plunge into, you are guaranteed to find something that you have not encountered.And so it turns out that some seasoned specialist with 10 years of experience can still afford to join the project, on the basis that he knows a lot, and what he does not know, he will finish his studies. And what about those who don't have even a couple of years of experience? I will say for sure: for such people it is almost hopeless.
. , ( , ). , ?
, :
() , ( , , , ), .
, , .
, , . , .
. , php, MODX . , , , . , .
JS : . , . - , ( ).
, " ?! , !". : " ?". , - ? , , , ? , , . , , "". . .
: . , - , , . . , , . , , : , , .
, . , , : - , hh, , .
, ?
Git
, . .
TypeScript
TypeScript - , , , JavaScript, .
?
, , , - ( ..). TypeScript . , , , , . , . , . - , JS , , - . , , : ? ( , )? ? JS, , , ( ).
TypeScript, , - IDE , . - , TS , " , " " , , " .. , " ", " ". . " ", , : " ". , , . , . , , , , IDE , , .
: JavaScript, TypeScript. . , .
React
React . Vue, Svelte .. , React. : , . , , . - , , .
Styled-Components
- - JS+HTML+CSS. CSS , SASS, LESS .. , styled-components. TS+React -, , , . .
GraphQL
GraphQL API , GraphQL. , , , . , API-, GraphQL , , , . ( ), .
Next.JS
( , ). . , ( SSR (Server-Side-Rendering)), ( ) .. , - , . Next.JS.
Next.JS - - JS+React ( ). ( GraphQL, Prisma, Nexus, Styled-Components ..). , 90%+ . ( , ).
, . , Next.JS , HTML-, API, GraphQL. , zero-configuration.
, , - . - . : , . , (- React, - Styled-Components, - GraphQL). . , , , , ..
. , - , . . , -. . , , - .., , , - , . .
, , , , , .. . , . . , , " - ". . , : https://freecode.academy
I will clarify right away that this is most likely suitable only for beginners and only for those who really intend to learn something. That is, you will have to make efforts and the first tangible results will be only in two or three weeks, and at the commercial level it will take at least two or three months. But I guarantee that on my part all kinds of help will be provided to the students, and all this is free.