Hello everyone

I'm new to the forum and glad to see that this "field" of programming has such a huge community.

I've been interested in game programming for a long time but was also aware of the effort one has to put in since it's

(in my opinion) on of the most demanding (and time consuming) topics.

During studying I enjoyed C++ the most, sometimes getting nuts with those pointers but kinda interesting though.

So, I'm close to finish working through the C++ basics and tried to get a feeling would could be the next step

Currently I'm reading Beginning DirectX 11 Game Programming by Allen Sherod. It's a good book but covers also

a lot of topics that seem to my "advanced" or just out of my field of understanding.

So I tried to grasp some other parts that are also included in Game Programming , like engines and this sort of thing.

When I attempted to find some information about working on a own game engine, most the comments were like

"none actually works on an engine on it's own since it's too complex"

Right at the moment I'm a bit confused on where to work on.

For me it feels like a huge step from C++ basics to working with directX11.

The problem is, I don't see thr "red thread" and I'm also not quite sure whether this thread even exist in this area of programming.

So what would you think to work on next?

Whom ever just voted me down, How about an explanation on why!!! If you disagree with my or anyone else "OPINION" the state why.
My above "Advice" is based on personal experience in the learning curve and I see nothing wrong with it.

Voting someone down for BAD code is one thing. Voting them down because your experience may be different is simply CHILDISH. especially when you offer no opinion of your own.

As Eddie said, start out with an existing 2d engine. SFML, SDL, pick one and make a couple simple games, then make a couple more complex games. This is a useful (and for most people, necessary) stepping stone to 3D environments.

Work on keeping data and logic separate. Then work on keeping data out of code and in separate files (initially as text, later as binary). Familiarize yourself with the STL, not only as a tool to utilize in your programs, but as a guide for developing your own tools. Try to reuse as much code as possible from your previous games in your new games. Initially, you'll find very little code you can reuse (or at least reuse easily), but this should get you thinking about how to write your current code to make it more reusable in the future.

Learning the syntax of a language is really only the first step to becoming a developer. The next step, and it's a step you'll be taking your entire career as a developer, is to learn how to use that syntax not just to accomplish your current goal, but to make accomplishing future goals as easy as possible (sometimes those future goals are to come back and support/maintain this current accomplishment). The beauty of this second step though is that it is largely language agnostic. What you learn in this life long step will carry over fairly easily to the other languages you'll eventually learn. And any remotely successful developer inevitably becomes multilingual.