Game Development

 For a comparison, let's compare work of a game coder to a level designer. void jump(int macro); and level designer: Monster island is hard to reach and that has to be changed on the level map. As you can see, obvious difference in difficulty.

 Consider the following C++ sample: int main() {     std::cout << template_1() << '\n';     return 1;      } Every moron who knows C++ would know what this means. Now consider that almost every line is a regular expression, so try to translate it into your native language, English for example; line by line in steps. ... rofl lol oO? I tried to do that with the example and my head almost had a system shutdown.

The hardest part of making games is coding. It is really hard to learn and even harder to apply. I'm not trying to say game design, level design and story writing are easy, but they don't even compare. Coding means understanding machine code in normal sentences. Line by line. Which is like seriously hard to understand. Try understanding a novel. Then imagine reading a couple of mathematical and crypted expressions and explain them in your native language. ...omg what the !!! does just happened ROFL? I'm sure if you just tried that, you have a headache.

 Like I've said in the last post, you should try using Unreal Engine 5 as coding is hard, very hard. It takes an insane ammount of time to learn and work with once learnt.

Unreal Engine 5 is a good way to make games without knowing how to code(or yet). You can use coded blueprints and even ask your coding teammate to make you one. Blueprints are coded parts of a video game and you can literally design levels with them. An example of a blueprint could be a quest.

 A cool tip I can give your for code design is to draw the 4-6 main building blocks of the code and have the graph in-handy when coding.

Keep in mind this article is meant strictly for C++ game devs and not for application programmers or game devs of scripting/other languages. I have my own technique when it comes to OOP in C++. The game I'm deving right now(or we are making) is a simple windows console project. It's up to you to decide whether you'll use this technique. First let me tell you in which cases you might need this technique: if you're ready for a new look on OOP if you need a new toolset for your coding practice if you like to learn(which I clearly hope for) So, the technique then. Decide which you prefer more: classes or structures. This helps you understand what kind of objects you want in a game.