Project implementation mentor
Yan Zhiwei, a graduate student at Beijing University of Posts and Telecommunications
Recently, due to a project, I read the new book Visual C #2005 Program Development and interface design tips.
For a long time, I think that when I learn a language, students always start from the grammar step by step and get familiar with a compiler. When the syntax is proficient, I am familiar with a class library based on this language, and finally reach the overall architecture. In this learning process, I often get used to searching for resources on the Internet and reading the technologies written by others. Article To learn from others' experiences and learn from others' experiences. Code And there are only a few classic, basic, and theoretical books on hand, which will be available from time to time for further understanding.
However, when I got the Visual C #2005 Program Development and interface design secret from Zhang Limin, I naturally put it on hand and checked it from time to time. Why? Now I picked up this book from scratch, probably for these reasons:
First, Chapter Limin's "Visual C #2005 programming and interface design secrets" can be seen from the directory arrangement, which is a step-by-step process. It can be said that both beginners and junior developers have their own topics. Books are always suitable for you. It's too shallow to be perfunctory, too deep to be obscure.
Second, the style of this book is of the valid type, which is described one by one according to the terms. As mentioned above, this book is gradually written. You can learn from the beginning to the end. Another benefit of this book is that the terms can be read independently from each other. It can be said that it is a tool book that can be accessed at any time. Many of the books I have read in the past are often used in a whole article. This is an example, with very tight front-end and back-end adhesion. Such a book often needs to be read before and after, and a lot of confusion will occur if you need to grasp the author's ideas accurately and accidentally.
Visual C #2005 Program Development and interface design tips this book is good at this point, each article can be self-contained. For self-taught students, it is often impossible to read a book from start to end. For those who have a little programming Foundation, they always hope to quickly solve the problems encountered in programming. Therefore, the general logic of the content is strict, and it often means slow and stable deep reading. Such books are not suitable for any time to solve the problem. Visual C #2005 Program Development and interface design tips. What I have read is that every clause is a short and concise paper. You don't need to spend a large amount of time reading it all before and after, or you can jump to see what you like most.
To realize this advantage, you can choose to read a book similar to "how to use ......" "Use ......" .
Third, the example of this book is very good. It is not tedious, short, and lean. In addition, this book is very detailed. The operation details are clearly written step by step. While reading this book, I am not only familiar with the C # language, but also with a development tool Visual Studio. NET.
Fourth, when learning a language, we often focus on exploring and knowing it. Although this book looks like a tool book, you can refer to it when you encounter problems. However, in some difficult issues, we often talk more deeply about the issues and give them to readers. For example, some terms refer to "do I need to use the stringwriter class ?" "Create, sort, and binary search of object arrays.
Of course, a book is often targeted at readers. It is impossible to cover all aspects. Therefore, it must be relied. However, from the perspective of the whole, this book is indeed quite unique. There are no vague examples of impracticality, no large volumes of code, and no obscure theory. This is a book that emphasizes practice. I think we will certainly benefit from reading this book for students who want to do some projects.
