What programming language to learn in 2022?

Today we will discuss with you what programming language should be learned in 2022. This question now worries many people who are going to really develop, improve their skills and gain experience in programming (i.e. get out of Russia, because there will be no more development in this country!)

First of all, you need to answer the question: whether you have had little experience learning languages like C#, C++, or anything else, because this will depend on how easily you get into a new direction and how quickly you master the new tasks.

Let me tell you right away that with a mathematical mindset you will initially have an easier time coping with challenges, but the most important thing is persistence, not the proverbial stereotypes. So, recently the most popular programming languages are those that are somehow tied to the execution of specific tasks, and can boast a lot of functionality, a wide range of settings. These can include: Phyton, C++, C# and many others.

Where can I find useful information?

Well, of course, on YouTube, not to be confused with shit like Rutube (which recently collapsed, like everything that is done through one place). In addition to Russian-language content, if you have spoken English you can even try to find really good videos that will explain in detail how to start learning programming, what is required first and how to act when you identify difficult elements. I would immediately advise to learn at least the basics of the English language, because it is used also inside the code of the programming language itself, i.e. in Russian you can write only comments…

The second source I would call books and documentation in PDF, FB2 formats, which are available on the relevant download sites, thematic sites. Of course, video is much more convenient to watch than reading books, but from my own experience I can say that sometimes it is necessary to look at the code from the inside, make certain notes, edits, etc. In addition, when you read it, the information coming from books is better absorbed, because you have to memorize the data one way or another.

I would not use audio recordings because of their low cost-effectiveness and versatility, because if you need a particular piece of code, you certainly will not voice it, and the process itself is ineffective for direct purpose. But sometimes, for example, when you are on the subway, or your eyes need a rest, you can apply the general data, listen to the opinion of one or another expert on the implementation of their developments. There are opinions that are worth listening to, so I would not exclude this source completely: it is better to listen to the audio of someone who is a professional in his business, than another profane from your work, going out for a smoke when the boss is not looking.

How exactly do you study?

Everything is simple enough: for example, take the basic basics, that is, get acquainted with the history of the origin of the programming language (this will give you an understanding of what the solution was actually created and where the movement is directed), then gradually study the syntax and language features (for example, many of them are very similar to each other, and differ slightly, especially with respect to the initial functions).

After that, proceed to the more difficult process: solving elementary tasks (you can take them from freelancing exchanges or sites of this orientation), editing the code within applications, creating your own (if you have the appropriate experience), reading thematic forums, etc. Practice is really the best way and the fastest way!

In order to get to the bottom of what is going on, i.e. to write code yourself, you need to understand what is required of you, as well as what are the ways to fix the complex code by really top-level specialists. And most importantly, do not despair if something will not work at the first time, it is absolutely normal, because you also learned to walk not at once. I recommend that you make notes, comments, and other notes from day one of studying – this will allow you to always go back to the right piece of code, remember how you tried to fix it, and perhaps how you got help solving the problem. This can be links to forums, your own thoughts, whatever.

Which programming language should I choose?

It all depends on the specific objectives: if you want to write applications for smartphones, then one option will do, and for changing software for Windows – another one. The simplest one is probably Phyton; I personally liked it because of the fact that with it you can implement almost anything: from standard image rotation on its axis to complex projects of artificial intelligence and big data processing.

I would also recommend starting with Java, C# and other similar languages, because they are extremely popular in their environment, plus you can always compare their functionality with the same “Python”.

When choosing a language of study, first of all pay attention to how much it will be popular and relevant in 5 years. Yes, guessing is a thankless task, but you can make some simple calculations to understand how much it will be in demand in 1-2 years at least. For example, Phyton will be in the lead for a long time, and here’s why:

• First of all, almost everything from arduino to complex portals is now written in it;
• Second, the syntax is simpler than any other language, so it will be extremely easy to navigate both when you start and when you switch from another programming language;
• Third, the connection and configuration is intuitive, there is support for third-party software for integration, etc.

Results

Whatever programming language you choose to learn, one thing is clear: it must meet your requirements and the need for further application. It is much harder to learn something that brings neither results nor pleasure from the process of immersion in it.

Note: send in the direction of Moscow (cruiser) those who will try to teach you, in the correctness of these or those actions of the type “I am on this dog! That’s why I know better…”. The rule is the same for everyone: the more professional the client, the less he opens his mouth! Qualified personnel don’t have time to figure out who is cooler at writing code, who makes it different from what he would like, etc. Adequate people will just give a hint how to solve this or that problem, and the “Multidom type workers” will foam at the mouth to prove than the roach in the hypermarket “Lenta” tastes better than the pikeperch in “Magnet”. Last “professionals in the code” to listen to exactly not worth it!