Re:The Time Needed to Write “Effective Modern C++”
by jlarocco on Wednesday April 22, 2015 @11:21PM
(#9424850)
I largely agree with you, BUT, this version of Effective C++ was less opinion and style oriented and more a guide to avoiding easy to make mistakes with some of the new C++11 and C++14 features. Not following many of the guidelines will result in incorrect and broken code.
My recollection of the older books is that they covered "best practices," and ignoring them may have been bad style, but the code would still be technically correct. Quite a few are still style issues, but it's important to recognize the difference before deciding to ignore them :-)
Re:The Time Needed to Write “Effective Modern C++”
by sbov on Wednesday April 22, 2015 @10:31PM
(#9424697)
You should still read them though. But instead of reading them like an instruction manual, you should read them for an eye towards when you would disagree with them, when you wouldn't, and why.
Re:The Time Needed to Write “Effective Modern C++”
by lfowles on Wednesday April 22, 2015 @10:23PM
(#9424670)
> It is frustrating when people hang on to certain ideas just because a famous author said it. Sometimes it holds us back.
What I appreciate is that most of what he says (via GotW or the books) comes with the rationale and a code snippet instead of a blind assertion that this is The True Way.
Re:The Time Needed to Write “Effective Modern C++”
by Ragnarork on Thursday April 23, 2015 @08:56AM
(#9426326)
Scott Meyers mentions at the beginning of his books that his advices are important (according to him), but what's even more important is the rationale and why he gives you this advice, and I believe this is also a reason his books are great. This is not "Follow this guideline blindly", but rather "I suggest you follow this guideline and here's why".
My own personal feeling is that books like these can be invaluable for people starting out in the industry. It gives you a reference point to relate to. If he can explain things well and people can understand his writing, then it can be useful even if the person isn't the best living coder on earth.
At some point in your development, you need to branch out from what people are saying in books and start to form your own opinions. You have to start questioning what the "experts" are saying and try to experiment with other techniques. It is frustrating when people hang on to certain ideas just because a famous author said it. Sometimes it holds us back. It doesn't make their contribution any less valuable, though, because at least newbies are getting to a certain level due to the well written books.