How To Start or Continue Learning C++

I have been a beginner for 4 years in C++, mainly because I started when I was 16 and didn't take it seriously until now, but the best beginner resource are the one's that are the shorted and get you set up in 4 hours. The tutorial by Bro Coder is good for this. You don't need to worry about the high level features, because currently your projects won't require them. If you are remaking arcade games you don't need more than a class.

Ever considered to make a C++ Udemy course as a build up to OpenGL?

May I know how to make the cute 3D floating island? Any tutorial or sample code? thanks

The problem is that every tutorial covers all the basic programming stuff I already know from knowing other languanges,which means they waste a lot of time on things I already know (outside of the syntax).

Just make your own programming language in HTML/CSS if you don't like C++

How to restart ? ;)
I infused some knowledge about 1990 era ;)

I found your accent really hard to understand

this channel is a Diamond!

Enter me? 🤨

I prefer C, you have to write a lot of basic stuff, you don't have strings and custom operators, but aside from that I really think it's a better language.

what are all the programs you use do you only use opengl and visual studio or do you have 8 programs you use or something completely different?

Love your contents

Its so hard to me, and especially installing libraries and building. I never know what dlls to use and when i send my projects to friends it works on like some computers but not all

bença pai

You should learn and get familiar with RAII right about as you learn the std library, in my opinion. The earlier you familiarize yourself with the concept, the better, because that's widely regarded as the right way to keep memory management under control, and refactoring code to fit the structure after the fact is often not feasible.

For context, RAII, meaning "Resource Acquisition Is Initialization", is a simple idea: your objects should set up everything they need in their constructor, and release those in their destructor. In other words, you should never have an "Initialize" method.

Doing this has several benefits, but most importantly it allows the compiler to catch hard-to-notice memory management errors for you.

The legacy codebase I currently work on has not one, not 2, but 4 "Initialize"-like methods for every object (two Deserialization methods, an Initialize on creation and an Initialize on load) and the code is an absolute mess of locks and "if (IsThatObjectFullyLoaded(etc))"-like calls, and we have to fix bugs of the kind "I tried to use object A that depended on object B, but object B wasn't loaded yet" frequently. Don't let this happen to your project.

Thanks Dad

Oh yeah