2014 is about to pass, this year I participated in a lot of interviews, was asked a lot of questions. Come back to the conclusion found that they do have a lot of shortcomings in the foundation, there are a lot of things I do not know. In the second half of the purchase of books, and systematic study. The book I am currently reading is Jon Skeet's in-depth understanding of C # and Mastering C # Sixth Edition. The boss also recommended C # core technology but I haven't bought it yet. Proficient in C # This book is still good, covering a lot of knowledge, so also very thick, I have to use a chopper he cut into four parts, otherwise really can't read it well.
A new job in November, the field turned to financial it, the use of tools suddenly high up: The latest c#,.net environment, ASP. 5, most of which I've just heard and used before. Fortunately, the new boss is very good, look at my level this dish still did not fire me, but also every day to me badgered, refactoring I write out of the unsightly code, so that the project delivery date dragged and dragged. Now I finally have the opportunity to practice the new things I learned in the book, feel every day to learn a lot of new knowledge.
Today, the establishment of the blog park, before also read a lot of Bo friends of the article, the harvest. I hope that I can persist in blogging, recording the story of my growth, but also share with you some of your own small experience.
The topic of C # is huge, and the whole OO concept is added to the word. But I don't want to delve into OO because I'm not very thorough about it. I would like to summarize the following aspects, I think these are the essence of C #:
1 delegation and its evolution
2 LINQ and the technologies that support it
3 Async and its evolution
I think it's a good C # programmer to master the top three (at least it will). In fact, the second topic used in the technology is the first topic in the foundation of Good (LINQ inside a large number of delegates), so there are actually only two topics. These three topics one big game, and dig into the details will make people feel that the brain is not enough, then doubt their IQ. So I think there's no need to delve into the details of what the compiler can do for you, unless you have special needs such as performance comparisons. But I'm not up to that height myself.
Later articles can be regarded as the type of reading notes.
C # Self-study Series-Opening