Some things I want to say about my new book on WP8

My new book "Windows Phone 8 development skills and case studies" has been published and has been purchased by some readers. Here, I want to explain something more here.

I strive to do my best, but it is hard to make a conclusion if I can fully satisfy everyone's needs. My foothold is to pick out more common and practical skills for WP development. In my original intention, I will not cover all the content. After all, books are for reference, not dictionaries.

I have read many programming books before (but I have bought only three books, and others are provided by libraries ), from the Visual Basic 6 book to the C # programming all-powerful dictionary I bought two years ago. But to be honest, I am not satisfied with many books, especially those in China. Really, from the heart, at least I personally think so. I used to read other people's books. I didn't read books for the purpose of reading books. I have been wondering why, obviously, this knowledge is very simple, and the book is so mysterious, I still use five or six pages of paper. Is this necessary?

I tell you without reservation that I have read many people's books, and I really admire three of my predecessors:

1. Mr. Sun Xin. I admire sun in my heart. Whether it's his VC ++ video tutorial or later book "VC ++ in-depth explanation", it makes me a treasure;

2. Mr. Zhang Limin has written many books and I have read almost all of them. They are really nice. I have read Visual C # Io and data storage twice;

3. Mr. Jin xuliang, I believe many of my friends have seen his masterpiece. He also advocates IT education innovation and his ideas are greatly influenced by him.

For a long time, I have been learning and exploring a path: Why do others always say programming is hard to learn? Is that true? Is it really difficult to get started? I often ask myself this question. Is there a way to get started quickly?

Many training institutions often use the "quick success" flag, which leads to misleading many people. Even I often hear other people ask: "How can programming be fast? Two weeks ?" When I heard this, I almost vomited blood and did not speak. Then he said, "I should be proficient in that month ." I have heard of almost lack of brain cells. How can I be proficient in a month? Scared!

I think the Quick Start I mentioned is not to say that I can lay a good foundation in a month or two, but simply to relocate all kinds of knowledge points and simplify the traditional model, turn abstract and difficult things into objective and real things. If you want to learn martial arts for two months, you can try it. I dare say someone else can beat you to the ground.

I think everyone should really study with Zhuge Liang. How many years have Mr. Wolong spent in Wolong? Of course, we are modern people, and we cannot stay there for 27 years as an old man. We are learning the spirit of people, learning their way of thinking, and learning their ways of doing things. Although the times are different, we are still saying "The days remain the same and the ways remain forever ".

Really, now many people are too impetuous. I have to say this: speed is not up to speed. Do you understand? I told you to hide your secret, not to let you do nothing. If you want to do something big, you have to fill up the feathers on your wings. Otherwise, do you want to fly? If you fail to fly, you will suffer from scars, and your health will be broken.

 

One of the most serious problems for many it books is that they either copy the translated version of the document, or translate the English document into the book. Isn't that the purpose of the article? Why are you writing so thick books?

I have made a long-term comparison and try to find that instance teaching is the most effective. You think about it. Why? Do you want to talk on paper? After all, isn't it for use? This motivation is pure, so books should tell readers how to use this thing and give more examples. Isn't it better? Do you have to be so angry with me that you don't even know what it is?

 

No matter what you learn, you can learn Photoshop, CAD, or programming. To learn it, you have only one path, more hands-on, and more hands-on. How do you know if you know this thing? This is often the case. When reading a book, I feel like I know how to use it. However, my mind is blank as soon as I get on the machine, and I am in a daze when I open the development tools, the results cannot be obtained. Many people have encountered this situation. Have you ever wondered why? There is only one answer. If you do not want to use it, you will not be able to use it in a few days.

Think about the geometric mathematics you learned when you were in junior high school. If you have never used it, when you graduate from college and come out to work, it is estimated that few people will remember it, even simple proof questions cannot be proved. Do you think about this? That's exactly how familiar is.

 

Therefore, I would like to raise a few requirements for readers and friends. I hope you can do this. I will be very happy to write this book.

1. For every example in the book, it is best not to start with the book.Source codeInstead, try it on your own as much as possible.Code. No, you have to copy it to me. If you don't do it, you dare not take the first step. How can you upgrade yourself later? I think it is a good thing that books do not contain CDs. If you want to download them from the official website, you will not copy them on the CDs at home. I do not like other people's copy work, do not copy other people's things directly to say it is yours, so that I will often be unhappy.

2. The examples in the book can be transformed based on your ideas, turning 100 instances into 200 instances and then 400 instances ...... As you can see, you have learned a lot. I strongly encourage you to do so by extending the Knowledge mentioned in the book to multiple knowledge points.

3. Apply the learned knowledge to actual development immediately. It doesn't matter if you have no actual project development. You can also think about what you can do and do some small applications, technology doesn't have to be improved in real projects. you can do some gadgets by yourself to improve your skills.

4. There is no absolute correctness and no absolute error. I hope you will not be superstitious about books. I have always stressed that not all the content I have written is correct. When I went to college, a teacher told me, "after reading a book, if you do not understand the content in the book, you fail. If you master everything, you are barely qualified. If you overturn everything in the book, you are amazing ". So, if you can overturn what I wrote, it means you have made great progress.

 

I hope this book will be helpful to all Windows Phone developers, so that my efforts will be worthwhile, even if it is of reference value. Thank you.