Learning c# by creating games, is it worth going down this path and what are the options?

Question

C++ / C#

Good time of the day.
So fate happened, I got on a big project written in c # windows forms. I know, the technology is old, and desktop applications are not in trend at all now. Previously worked on the web, php, a bit of js and other typical technologies. All programming consisted of fetching data from the database and inserting it into html.
I want to learn how to code, how to code well. To do this, you need to read books and project the acquired knowledge into real applications. Plus, the desire to show a creative streak. It seems that games are more than appropriate here: coding, design, interesting story. I like to wander in indie games, I was impressed by limbo, brain. Googling, I found the uniti3d engine, where you can write c# scripts. However, from what I read, I realized that you don’t need to program in it at all to create games, you just drag and drop ready-made elements, and this is not entirely consistent with the goals.
Interesting development for mobile devices. Windows 10 is heard to provide a single platform for building apps across devices. But it is unlikely that these applications will be in demand, at least for 2-3 years. This niche is firmly held by other operating systems.
Maybe this is a bad business and it is worth joining some open source project, something related to AI.
I recently wrote a "minesweeper" on windows forms and it turns out the devil is not as bad as I thought.

Answer 1

Programming happens in the head. The computer is just a means of expression, just like windows forms. Train yourself to write not only code, but also documentation. In general, the programming of games is not at all like a game and is overgrown with a bunch of additional work that you don’t always want to do, because a) I saw it a million times from others and b) I thought it should work on its own, but it turned out that I need do something that users will tend to "skip" as an annoying obstacle to the action.
From small observations of the profession - just make one or two discoveries / insights for yourself, but every day. Keep up the pace, keep running. :)

Answer 2

All of the following is only related to the development of normal games and serious programming, and not to crafts on the knee that bring zero profit.
1) In Unity3d it is NECESSARY to program. You won't get off with dragging ready-made elements. Those who claim otherwise are blatantly lying.
2) Creative in terms of interesting stories and the like, non-programming for programmers in games is not enough. First of all, game designers are engaged in creativity there. And you will have time to hate them, rewriting some never creative module three times.
3) You can learn to program well ONLY in a team.
4) Usually what the application is written in does not really matter. Approaches, patterns, algorithms, and other buzzwords are important.
What conclusion would I draw - continue to work where you work for the time being. If the project is big there, you will gain experience, and it is always needed. If it really itchs to make games, join some ADEQUATE team. You can try to look for them on gamedev.ru, although it can be extremely sad with adequacy there.

Answer 3

By creating games on Unity3D, C #, you will learn for a long time. And you won’t learn it well, due to the differences between the normal approach and the one in Unity3D.
There are no constructors ( Awaik, Start ), some obscure methods are already inherited in game objects, etc. This is not bad, but it's not pure C # either, there are many nuances from the Unity3D engine itself. ( This is the impression after reading the official reference information in full )
From what to read:
1) Jon Skeet C# for professionals. Programming subtleties. ( Gives a general understanding of .Net and C# )
2) Jeffrey Richter CLR via C# Microsoft.NET. ( deeper knowledge in places )
3) McConnell - Perfect code. ( put your thoughts in order )
4) Martin R. Clean Coder. ( a small book, also tidies up the mind )
5) Krzysztof Cwalina, Brad Abrams "Software Project Infrastructure: Conventions, Idioms, and Patterns for Reusable .NET Libraries". ( very powerful book, teaches how to write, not just write what would work )
The first two are about code, the rest are about writing rules, the importance of which you will feel over time.