Member Avatar for revenge2

Ok so after quite awhile i finally picked up from where i stopped last. Which was the "2nd" page of the book "sams teach your self c++" lol!
(im not much of a reader)

But today i intend to start work properly and continue learning c++, so i would just like to know if there is anything that i can do whilst going over this book.
any insider tips i should know etc...

-thanks.

  • 5 Contributors
  • 4 Replies
  • 101 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by toko

Dani AI

Generated

Picking the book back up is a good start. Combine reading with a disciplined, hands-on routine and the learning will stick faster than by just skimming examples. As suggested, treat any single source as one perspective; as and implied, dig into concepts rather than memorizing, and actively retype and change examples instead of only copying them.

Set up a small, modern toolchain and use it every session. A current compiler (g++/clang/MSVC) plus a simple editor or IDE and the debugger will pay off. Enable warnings and a modern standard when compiling (for example, g++ -std=c++17 -Wall -Wextra) so the compiler helps catch fragile habits early. Keep an online reference handy such as cppreference.com and a clear beginner guide like LearnCpp.

A practical weekly workflow:

  • Reproduce a chapter example from memory, then extend it (add a feature or change input/output).
  • Build tiny projects that force using new features (calculator, text parser, basic data-structure implementations).
  • When stuck, reduce the code to a minimal reproducer and read compiler messages closely; search precise error text and a reputable reference before guessing.
  • Track progress in version control (git) so experiments can be reverted and compared.

Keep modern practices in view: prefer the STL and RAII, handle resources with smart pointers rather than raw pointers, and learn why move semantics and const-correctness matter. For longer-term depth, consult the C++ Core Guidelines (isocpp.github.io) and revisit older book examples to identify outdated idioms. Following that cycle of read ā†’ type ā†’ extend ā†’ debug makes the book much more useful and prevents common beginner traps noted by .

Recommended Answers

All 4 Replies

Member Avatar for Hamrick

The best insider tip I can think of is don't trust everything you read. Keep an open mind because what you learn could be wrong and you have to re-learn it from another source.

Member Avatar for gauravsharma132

the insider tip firstly be passionate for c++.and secondly dont grasp anything just go to depth of the concept.not able to understand from one book ur reading.serach ur problem in other books until u clarify it.

Member Avatar for avgprogramerjoe

I'm using the same book. I hat how it gets you to just edit the code it gives you. Put your code to the test. Think of simple things to make, even if it is really corny.


Joe

Member Avatar for toko

hi am am also a newbie nad reading the same book what i like to do it to test myself and whnever there is a script in the book i ry to guess what it does and the read the output and analysis. Also i advise you to have a compiler ready and as you learn you write some stuff to test yourself and so you study corectly.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.