I can't say learning C++ is the right choice, but it is beneficial to know. I started with Zzt OOP, maybe some perl. But one thing I had been doing was reading, "Teach Yourself C++ in 21 Days" I never finished, didn't really write any C++ but that was a helpful book overall.
If you started with "maybe some Perl," you are immediately and unquestionably an OG on this site and forever.
Don't let the young-uns phase you. There's nothing that can be expressed in any client side language that you haven't seen, grokked, and dismissed as a Perl regex or some shit. :D
This was the 2001 edition. I like some of the analogies used to explain things. Like speed dial for memory addresses (pointers). It did a good job of building on the previous examples. It has been a long time but The D Programming Language by Andre is the only other book I feel drives the principles to programming as part of the content.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I can't say learning C++ is the right choice, but it is beneficial to know. I started with Zzt OOP, maybe some perl. But one thing I had been doing was reading, "Teach Yourself C++ in 21 Days" I never finished, didn't really write any C++ but that was a helpful book overall.
If you started with "maybe some Perl," you are immediately and unquestionably an OG on this site and forever.
Don't let the young-uns phase you. There's nothing that can be expressed in any client side language that you haven't seen, grokked, and dismissed as a Perl regex or some shit. :D
Helpful in what ways? about the book
This was the 2001 edition. I like some of the analogies used to explain things. Like speed dial for memory addresses (pointers). It did a good job of building on the previous examples. It has been a long time but The D Programming Language by Andre is the only other book I feel drives the principles to programming as part of the content.