Question from the interview; What is the main theme of Effective C ++?

At a recent interview, I was asked the following question:

What do you think is the main topic / one word that sums up the Scott Meyers Effective C ++ series?

What will be your answer to this question?

+4
source share
10 answers

In one word Advice

+13
source

My answer will be "I'm not sure, I learned C ++ without reading this book."

+8
source

Two old editions have put together tips that are especially useful for people switching from C to C ++. Using new / delete instead of malloc() / free() , and OOP was new in 1991.

The 3rd edition focuses more on people switching from other languages ​​(Java, C #, etc.) to C ++. It comes with tips on patterns, patterns, exception safety, a much richer standard library, and many other topics that people did not think about in 1991.

Basically, the goal of Scott Meyers has always been to write "the best second C ++ book to buy" - not just to teach you a language, but to become a true professional. He wanted to list the "50 most important tips for practicing C ++."

Oh, and something that we must not forget: he wanted this (and succeed) to be a technical book, interesting to read.

+6
source

Although a very strange question to ask in an interview (given that your candidate may not have read such an excellent book ), I would say that the main topic of Effective C ++ is the path to a semi-expert C + programmer + and adjust his / her way of thinking (especially regarding the internal elements of C ++) on the way to becoming an expert.

One thing I learned a lot about is link self-control (Page 71, paragraph 17). Better memory management. The preference is new / delete vs malloc and free (which is obvious, but his argument was very well stated). Another good thing is paragraph 29 on page 123, so as not to return β€œpens” to internal data.

It is not easy to read, and it is definitely not a beginner's book. This is another leap for a C ++ programmer who wants to become the best C ++ programmer.

It was a very good book, and although it is dated a little, it is one of the best books to become an experienced C ++ programmer. I still read it so far, and I'm definitely not an expert in C ++; this is a hobby.

To impress the interview, you mentioned that although you liked Effective C ++, the interviewer should take gander to More Effective C ++ . Explain some of the advantages of this book and ask if they also read it, given that they read Effective C ++. That should kick a piece :).

+4
source

That C ++ is an insanely complex language with many tricks, tips, idioms, and odd constructs that you should know by heart, and not be imposed by a good language?

You may not get the job anywhere except MSFT, though!

+2
source

Not

{blah body blah too short}

+1
source

C ++ gives you enough rope to hang yourself. However, you can write solid code using this if you follow these guidelines.

+1
source

Recommendations for writing better C ++.

0
source

The main (plagiarism) theme: "Great responsibility comes with great power"

0
source

How to write efficient C ++?

0
source

Source: https://habr.com/ru/post/1302774/


All Articles