Landlord recently in finishing two books reading notes "effective C + +" and "TCP/IP Detailed Volume 1: agreement", these two are classic books, notes also have some. Because the main is to talk about "effective C + +", so the book has been written out of the directory listed, This directory will not be updated .
"Effective C + +" directory:
The 1th chapter of effective C + + makes himself accustomed to c++-reading notes
Effective C + + 2nd structure/destructor/assignment operation (1)-Reading notes
Effective C + + 2nd structure/destructor/assignment operation (2)-Reading notes
"Effective C + +" Chapter 3rd resource Management (1)-Reading notes
"Effective C + +" Chapter 3rd Resource Management (2)-Reading notes
"Effective C + +" 4th Chapter design and Declaration (1)-Reading notes
"Effective C + +" 4th Chapter design and Declaration (2)-Reading notes
"Effective C + +" 5th implementation-Reading notes
"Effective C + +" 8th custom new and delete-reading notes
Yes, I'm not going to tidy up the effective C + + in this way, but the TCP/IP detailed Volume 1: Protocol will continue to follow this way, for the following reasons.
the effective C + + "This book, I have seen a total of 2 times, but only today found that their own notes are too" college pie. "
Strictly speaking, I don't think there is anything wrong with this way, but one thing is certain, it's too "laborious". I found a note, I will spend more than 2 hours, this is I read the relevant chapters 2 to 3 times times, of course, I also pay more attention to the format, if you have a large monitor to see my notes, may be more comfortable, font is larger, I think the focus has color tags.
From the content point of view, I think this book is mainly the language characteristics and design method two parts ( really is a personal poor opinion, you found me really very dishes ):
Some of the terms are actually the language basis, you know, you know, do not know to see the know, this content to do a small demo on OK, see the people understand, oneself of course can also recall the content of the provisions of the demo;
Some of the terms are relatively ( just for me ) feel a little "chicken Soup of the Soul", I mean I can not resonate with it, no way to develop less experience. For example, the compilation dependencies between files are reduced to the minimum clauses, and so on. This Part I will not write in the notes, because I do not understand, but also take out what to do.
Some of the terms are only part of the content I think is very exciting, the other part of the content for me a little "wide", understanding is not enough, so "wide" this part will not appear in the notes.
Recall that their original intention to do reading notes, is to facilitate their quick review of the classic content, replace the paper version of the book, open the ipad direct reading, I found that I really like this way of reading, in addition to the real paper version of the book quite a lot, there is no place to save the local PDF version can also be seen on the road. Feel a lot of content can be echoed in the head ( I really can't tell if this is a kind of rote memorization?) ).
So, I'm going to change a new way to write "effective C + +" Reading notes, content to show part of the terms or conditions mainly, to dilute the concept of which terms. General first through the demo to explain the existence of the problem, and then analyze the usage. This approach can be a short description of the problem, but also to facilitate me to add content in other books. Some of the C + + books I've been reading are as follows:
Deep Exploration of the C + + object model:
Explain the C + + object model, or need to know, I read chapter three.
"More effective C + +":
and "Effective C + +" is the same author, although the terms are few, but the content is not small, of course, some with the "effective C + +" content is repeated, do not know whether the author forgot he had written . I haven't finished reading the book yet.
"More exceptional C + +"
The book was temporarily prepared, adding something generic.
The rest of the C + + classic books, I have the electronic version of the. Well, e-book I always jump there for a while, jumping back for a while, with limited key levels.
Landlord at the same time every day to read some "effective STL" clause and source code, for some codes feel very good, but is suffering from the "effective C + +" series of notes really "slow down" the progress.
So, I'm going to complete a new series of notes: Combine everything above and cross a variety of books. But it will be presented in a simple example, I have not thought of a good name, of course, the content is relatively shallow, after all, the level is placed there. But my habit is not to write not to read.
I think reading notes is very important, so I have to read an extra-curricular book for many years to extract some small sentences. the importance of notes now, even if you no longer review what you write, but the process of writing is more than you see (for me).
I found that a lot of seniors have not been interested in C + +, I have just started C + + as a "bird", but I still insist on doing this thing. And I do not think C + + features how difficult to understand, can not understand the temporary release, and then review Bai. This is really not a problem in terms of the overall change in customer demand.
In addition, I was a Python enthusiast, using it for the first time I felt the feeling of flying. I previously developed a software project that was C + +, and that feeling was really "sour." I'm going to write Python stuff behind me, too.
I look at a predecessor's blog that there is such a sentence: the current technical level of a technician does not represent his future study and progress . With everyone to encourage, really is very touched. I used to learn to do arm and DSP development, and finally slowly adjusted over.
I do not know if anyone will see my diary, the more I write more journal, while the weekend less people. Here is a picture of the end of this article:
Read "Effective C + +" experience and view and plan for reading notes (personal feelings)