The reading note can play the role of the outline, and the knowledge points of each chapter are reviewed, classify, and pay the paper, and put the key points of the chapter to the knowledge point. Write out. This process itself is also a learning process.
There is a process of taking a reading: reading the book and reading the book. That is to say, I have mastered the key points in the book, understand the content of the book, that is, "reading"; then chew the knowledge in the book, plus your own understanding, opinion, reopening, application, "reading thick" . The software industry has different new months. The new knowledge of new knowledge is endless, and the quality of one of the important media of these new knowledge is also uneven, it is worth spending time, and the self-reading book is not much. At the beginning of learning .NET technology, I chose two books: Standley B.Lippman's "C # Primer" and Jeffery Richter ".NET Framework Design", the former explains the knowledge point of C # in an instance, with "C Primer" phase More than a lot, no feature, fortunately there is no error, barely accept. The latter is indeed that the master is, although the understanding is the basics of .NET and C #, there is a kind of "from the inside out" feeling, with the former with deep and delicate. Do this reading note, read this kind of book, reading thickness is worth it.
In view of my understanding of .NET, I just started, so this reading note is impossible to reach "reading thick", but I tried my best to sum up the knowledge points in the book, let you look at the reading notes. The role of review is also content.
Finally, I hope that you will add more comments to supervise the successful completion of this reading notes. Thank you!
