Recommended books for. NET software design/Development Engineer

For. NET software
Several books recommended by design/Development Engineer

 

List several books that have had a big impact on me over the past year. Thanks to the authors and translators who have helped me with these books. Thank you for your hard work. I hope these books will be helpful to those who need them.

 

First:Analysis of Design Patterns(The2Version)

If I recommend a design pattern book, I agree with it. This book makes a huge change in my design ideas. Thank you, Alan. I have read this book about four times, and I have done Design for every one or two small projects,
Development, Review & refactoring and review this book. Learn from the newest, and be honest!

First of all, the biggest help of this book is to let me truly understand the power and elegance of OO ideas. When I went to college, I only understood object-oriented concepts. The Code process was basically based on process-oriented thinking. The refresh in my programming thought made me seem to have entered a new world. During that time, I was so anxious and excited that I was addicted to using OO to think and design and develop software. It is not easy for each of us to accept a new idea. Although OO has been around for many years, however, through university education and learning, it is difficult for us to understand the importance of code maintainability. We need to use real projects, excellent books, and enthusiastic mentor to help us learn new ideas.

Secondly, this book helps me to learn the design model. Based on several design principles derived from Object-Oriented Analysis and several common design patterns, I learned how patterns is going. The training background of the author has provided a lot of help for the ease of understanding of this book. Thanks again to Alan for writing this book. Although the model of this book is incomplete, I think this is quite good, and 23 models do not need to be fully integrated. For most of us, the commonly used models for daily development are basically enough, I can continue to learn more about these concepts.

This book can be translated. It is rare for me to take a picture of the table. If you are a newbie, we recommend that you take a look. I have also read this book, Martin.
Fowler's refactoring,
And head
First design patterns, both of which are good and worth reading. Li Jianzhong's lecture was quite good. It was a little long and tired, but I seem to have heard it twice.

 

Second:CLR via C #

This book is definitely about. net.
Framework is the best book. I have read more than 3-4 times, and some chapters have to be flipped through. My memory is poor. It's too far away from the boss. Hey, Mom, why don't you make me smarter. I mainly see this book translated by Li Jianzhong GG. The difference between the two versions is not very big.

Li Gg's translation level is really 8 wrong. I like it! I have read this book and have a clear understanding of the entire. net design architecture. Although I still don't feel good about the underlying layer, it is not easy to write a book like this. Like Jeffrey very much
Richter's writing style is easy to understand. In-depth and simple enough. Special chapters about exception,
Garbage collection, delegate & event, asynchronous
Programming Model (APM), thread &
Concurrency's explanation and analysis are really good, and it's hard for me to find a book that matches this in the market. Most of my understanding of. NET Framework comes from this book. This book writes less threads synchronously, and these two topics are quite complicated. It is really difficult to write the robust code. I mainly read Programming
The. NET components book was written in conjunction with Jeffrey's training handouts. Juval for APM, thread,
Concurrency is indeed well explained. Combining Jeffrey's book, the basic. net
Framework. Basically, I do not read any C # in this book #
XX books, too lazy to read, easy to get angry, huh, huh. If you read only one. net book, that is enough.

 

3rd:ProgrammingMicrosoft ASP. NET 2.0 core reference

Asp.net I have read this book carefully. This book is a little tiring. It is really a reference, just like a normal XX document. However, I have never seen any Asp.net book that deserves my appreciation. The focus of this book on ASP.net is basically covered, but it does not seem so easy to understand. I mainly read the first and third parts. The first part is about Asp.net.
Programming Model, I think it's quite good, like page
Life cycle and Asp.net runtime are all described in detail, and common control categories are also well organized. The third part is very good. I like it very much, especially the state
Management, httpcontext, httprequest, httpresponse, and so on. There are also basic security issues. This makes it possible for Asp.net
Infrastructure has a clear understanding of the global framework. Server
Thin in Design
Gg wrote a book, but only read a little, there is no motivation to continue reading it.

 

 

Fourth:High Performance Web Sites

Almost all of the 10 rules in this booklet are the essence. My personal primary interest is in background design, but I like this book and read it many times, after reading this, let's take out our website and compare it to see which ones can boost performance. this book is most helpful to me to improve my understanding of the B/S front-end, especially the front-end performance.
The summary of tuning also helped me to learn more about HTTP. I personally recommend you read ggdd and I strongly recommend you. If you haven't seen it, read it. The author is quite "da ". I like such a book. It's thin enough. I don't have to read it, and I have a rich harvest. After reading this book, I can be fooled with my boss. They usually fooled me. This is my turn to fool them. This book can quickly improve the experience of front-end optimization. If there is any book that can quickly improve my experience in a certain field, I am absolutely willing to read it. This investment is definitely worth it.

 

Article 5:High Performance MySQL

What should I do with this book? It mainly deepens my understanding of the database and is a high-level book on the database. We often cannot wait for the DBA to give us SQL
Tuning, maybe the project is a small project, where there is a DBA or project prototype, many times we have to rely on ourselves. This book systematically explains many MySQL mechanisms: Storage
Engine, index, replication, etc. This book is rare. The author seems to be in Yahoo! Worked. Basically, I started to spoof people around me after reading it twice. It is estimated that you are willing to look around. J. In the past, I only had to nod my head and think about what mentor said. After reading it, I can basically stand on the opposite side of the level and start to PK. Most of our daily development storage still depends on the database, so if we choose to learn a storage technology, we still need to access the database. Google's bigtable, hadoop, hbase,
Hypertable is also a pleasure if you can meet these ideas or projects. Distributed Storage + distributed computing is a great challenge.

Database Tuning should not be a concern of DBAs. Our daily design background developers should also understand some basic methods. MySQL also has a book about internal, which is a bit too deep. If you are interested in geeks, you can dig it up. If you have any idea, you can fool me.

 

 

Postscript:

There are already a lot of five books, and I hope it will be helpful to those in need. These books are indeed of great help to my past work and thought refresh. Thanks to these authors, they have spent so much time and experience organizing such excellent books. Thank you. If you have a good book, you can also recommend J to me. Don't hide behind your browser and give me some advice. In fact, there are still a few good books, but do not want to write too much into the garbage, just list: Pro
Javascript techniques and Dom
Scripting is helpful for me to learn JavaScript. For details about TCP/IP, http:
The definitive guide, programming collective intelligence, and more books about basic theories. The basics are important and determine the depth of a person's technology.