How to transfer your theoretical knowledge of the language to application development?

Question

C++ / C#

Good afternoon. I have a good theoretical background in C++ programming. The soul requires the creation of something more interesting than writing simple algorithms for solving Olympiad problems. The question is: how to use theoretical knowledge about the C++ language in practice? And what knowledge can be useful for writing a game (I don’t take into account the software component, graphics, etc.)?

Answer 1

Too general a question to give a specific answer. And there can be no good theoretical basis without practice.
The answer to your question is in the question itself:
Start implementing mini projects for yourself. Write a simple game with elementary graphics. In the development process:
1) you realize how poor your theoretical knowledge
is 2) you will see what problems you encounter during development in real life
3) you will learn about a ton of new methods / algorithms, logical and mathematical
4) you will understand what you want to do next, what projects to create

The soul requires the creation of something more interesting

Nothing could be more interesting than ai :)

Answer 2

Theory-theories are different, but in practice it is often necessary to twist things that no theoretician, even in the worst nightmare, will ever dream of. So you need to look for a task according to your abilities and within the framework of your knowledge and solve it. For in the absence of experience, an attempt to do something big is likely to lead to disastrous results, which anyway then will have to be completely rewritten from scratch. So the best option is to first learn how to do something small, and not just do it, but do it well. This will give some kind of base of experience, based on which it will already be possible to decide which project is more difficult to take. In addition, software development is not only writing code, but also designing architecture, modules and submodules, libraries, finding solutions, checking solutions, testing, choosing solutions, management, bug fixes, communication with users / clients / customers, UI / UX design and testing, writing and formatting documentation and a cart of other little things. In reality, writing code can be 15-30% of the entire project (depending on the size of the project and many other factors, of course). Often a significant amount of code is simply thrown away - 10-20% can easily go to /dev/null. Theory in isolation from practice is useless and is quickly forgotten like useless garbage.

Answer 3

Вот замечательная статья на Хабре, посвященная разработке игр для новичков. Если вкратце, советуют начать с крестиков-ноликов, не замахиваясь на 3D-JMMORPG.