I programmed professionally for 14+ years primarily in Microsoft languages but never touched C or C++. Began looking at some simulation technologies in 2009 and 2011 and ramped up on C++98 and C. Learned them well enough to produce results. C++11 came out and I did not give it much thought as I had already invested much in an established version (including the STL for C++98 and C-Style programming). After significant time reviewing books and materials in the context of C++98 from Nicolai Josuttis, Bjorn Karlson, and others, starting again with C++11 was not desirable. As C++ versions tend to be long lived and stable, I think that is still a good perspective.I have seen articles about improvements to rvalue references in C++11 and other statements from others regarding lambdas in C++11. In other places I have seen statements about how C++11 can improve the way code is written. None of that convinced me that there was an urgent need to understand C++11. Then I read a book by Artur Moreira called SFML Game Development in which he adopted many features from C++11. I am not a game developer, just researching cross platform graphics. Artur Moreira used C++11 quite effectively in his book and I thought that perhaps I should plan on reviewing C++11. When I saw several conventions of which I was unfamiliar while reading Artur Moreira's book, I decided it was time to review C++ all over again.C++11 introduces some useful concepts such as universal initializers, reference counting, and other concepts. Some of us know these concepts from our use and exposure to other languages. Microsoft C# has the concept of a foreach applied to interfaces of IEnumerable. It is similar in C++11 but presented differently. Rather than a foreach keyword with operands divided with an in operator, you have a for keyword with a : operator applied to a type with a pair of begin/end functions. I understand these concepts and can accept the syntax, but it aids productive use of these concepts to understand how they function in a concrete way as well as the philosophy associated with their use in the context of C++11.That brings us to Bjarne Stroustrup who wrote this book, C++ Programming Language 4th Edition. If anyone is going to explain the philosophy of C++11, he would be the top candidate. He invented C++. There are examples in the past of inventors who could not explain well their inventions, but Mr. Stroustrup is the exception. Perhaps due to his long, long history of writing and lecturing, in addition to his active participation in technology he explains theory and reality quite well. I have read some of his books from 10 or 20 years ago such as the Design and Evolution of C++ and maybe an earlier version of this book. I found his older books difficult to read and very obtuse. His writing in this book has shifted 360 degrees in which his words are in a fresh, contemporary style that is clear and candid.The most important benefit you gain from reading Bjarne Stroustrup's book is that you gain the perspectives, best practice, and preferred conventions for C++11. He gives advice and calls out common errors and where you might want to focus to have the code come out in a better way. You are NOT learning what is new in C++11 versus C++98. Instead, he is presenting C++ in the way it is today. This is important because you are not jumping back and forth conceptually between C++98 and C++11. He shows C++ in its new form in a complete and coherent way. This way, you can relearn C++ from a book that ties all the most appropriate parts of the language from start to finish. You can still keep the old ways in the back of your mind if you ever need them but he does talk about these things when necessary such as C-style casts (which I still use) versus using the bracket notation to convert type.His tone is very appealing. He does not speak about C++ dogmatically nor does he speak as if all is perfect. Rather, he proceeds through a presentation of C++ that unwaveringly emphasizes the right choices and considerations while admiting when some recommendation may not hold. The best example of that is in his discussion of the universal initializer. He makes an excellent case for the universal initializer, which I plan to use to maximum effect when I finally decide to enable C++11 compiler flags, but he also reveals ways in which the "universal" initializer may not be so universal. That candor makes the text much more valuable as it prepares one's expectations for what they may realistically expect in conforming compiler implementations of the C++ language.Again, I admit that I did not enjoy Mr. Stroustrup's books from 10 or 20 years ago. I reluctantly accessed this book because after a 1 year break from writing any C++ in my leisure time, I needed to look up some things. I thought I would just use this book plus Nicolai Josuttis' latest book on the STL as reference. I am still writing C++98 centric code and so the books as reference was somewhat less useful in some areas. However, as I referred more to this book from Bjarne Stroustrup, the writing style was so different and the explainations so much more clear that I was much more inclined to stop what I was doing and review the text in more detail. I decided now is the time to relearn C++ as there is now a guide that shows the way from start to finish.On that note, his book is a great manual on software development today. Even if you have experience, he describes a set of ideas in a way that if you thought about them more, you would produce much better software. He goes into the different types of programming styles (OO, procedural, generic, etc) and into low level versus high level providing presenting his point of view out of his extensive experience in languages, programming, and technology. He spends a tremendous amount of time on abstraction, structure, and code elegance through proper code definition. After reading his book you will definitely advance in your perception of software code.Me ... I am not a C++ programmer but someone with a professional background in software code who moved into C++ occassionally in my spare time in order to understand certain things in computer technology at a deeper level. C++ is in my toolbelt and I thank Bjarne Stroustrup for making it a more useful tool by way of understanding. I still do not recommend C++ for normal IT work, websites, and line of business systems better served by quick shift tools like Microsoft .NET and Java applied to frequently evolving circumstances. Rather, C++ is a language you can learn if nothing else but to better your cognition in the construction of code and the design of systems defined by code. The design and logical insights in this book are hugely valuable and he writes in a way where the concepts presented are digestable if you have any programming experience. You just need time and attention. C++ seems to have evolved well. It feels cleaner and more streamlined than even Microsoft C#. Admittedly some aspects of C++ remains inaccessible to entry level programming as part of a larger team and that is okay. Such things are necessary tools for more finely calibrating code in ways not needed in conventional IT (web systems, databases and batch jobs). I once perceived C++ as a low level tool with high level mechanisms. Bjarne Stroustrup has changed my perspective to see C++ as potentially a master language that works best when you understand it the right way.