Moving Ahead

[hassanAman]

Hello C++ Programmers,

I feel like I'm probably an intermediate sort of guy right now. Are there any suggestions that what should I do next. Like move on to graphics or just go on with the technical stuff. If so, which tutorials are recommended?

I'm probably a "pro" of these things:

1. Pointers/references
2. Classes/objects
3. Containers/templates
4. Polymorphism/inheritence
5. Loops (of course why not)

Thank you for your replies.

[Cubbi]

hassanAman wrote:

I'm probably a "pro" of these things:
1. Pointers/references

Is everything in http://en.cppreference.com/w/cpp/language/pointer and http://en.cppreference.com/w/cpp/language/reference familiar and boring to you (even int A::* const A::* p1 = &A::p; -- okay, that might be expert rather than pro)?

2. Classes/objects

Same question regarding http://en.cppreference.com/w/cpp/language/class and http://en.cppreference.com/w/cpp/language/object

3. Containers/templates

and http://en.cppreference.com/w/cpp/container and http://en.cppreference.com/w/Template:cpp/language/templates/navbar_content

If so, which tutorials are recommended?

Tutorials can, if you're lucky, give you a birds-eye view of what beginner level C++ might look like. For actually learning anything, you need a real book from https://stackoverflow.com/a/388282/273767 plus practical experience using debuggers, profilers, and other tools of the trade. Create something, or, better yet, fix bugs in something opensource that you use.

[JLBorges]

Stroustrup in 'Programming: Principles and Practice Using C++'

What comes after this book?

At the end of this book, will you be an expert at programming and at C++? Of course not! When done well, programming is a subtle, deep, and highly skilled art building on a variety of technical skills. You should no more expect to be an expert at programming in four months than you should expect to be an expert in biology, in math, in a natural language (such as Chinese, English, or Danish), or at playing the violin in four months — or in half a year, or a year. What you should hope for, and what you can expect if you approach this book seriously, is to have a really good start that allows you to write relatively simple useful programs, to be able to read more complex programs, and to have a good conceptual and practical background for further work.

The best follow-up to this initial course is to work on a real project developing code to be used by someone else. After that, or (even better) in parallel with a real project, read either a professional-level general textbook (such as Stroustrup, The C++ Programming Language ), a more specialized book relating to the needs of your project (such as Qt for GUI, or ACE for distributed programming), or a textbook focusing on a particular aspect of C++ (such as Koenig and Moo, Accelerated C++ ; Sutter’s Exceptional C++ ; or Gamma et al., Design Patterns ). ...

Eventually, you should learn another programming language. We don’t consider it possible to be a professional in the realm of software — even if you are not primarily a programmer — without knowing more than one language.

You may want to read this entire chapter: Chapter 32. What Do You Do After You Say Hello World?
in 'Ruminations on C++: A Decade of Programming Insight and Experience' by Koenig and Moo
https://www.informit.com/store/ruminations-on-c-plus-plus-a-decade-of-programming-9780201423396