Some Misunderstandings in iOS learning and iOS Learning

Some Misunderstandings in iOS learning and iOS Learning

1. dogmatism.

Discussion: blindly learn a book and blogs from some well-known iOS programmers in the industry. Of course, it will be adjusted in stages later, but we should discuss it here separately. There are a lot of books to learn, and I think that a good blog is vast. It would be a tragedy if I got stuck blindly. There will be a lot of possibilities. The most likely thing is that the efficiency is getting lower and lower, and there is a feeling that wow, those people are good, how should I be good, I am good, and I have a big gap, what should I do, it's over. In fact, there is no need to panic. If you have just started, pick a small and refined book and read it carefully. View a forum and a unit, and then find related blogs based on these sections. Rather than focusing on a blog of a person, it is not necessary to follow a blog of a person, because most blogs are fragmented and do not systematically introduce some knowledge points, and there is little link between them, A systematic blog with strong line to plane. Therefore, when the search engine technology is so developed and your knowledge system is not yet established, we recommend that you use the following methods instead of subscribing to a bunch of blogs. You find that there are more and more numbers on your RSS tool. This is rather painful. Come on. If you are a newbie, assume RSS.

 

Solution: Unsubscribe most RSS feeds. We recommend that you leave only 1-3 RSS feeds. Do not focus on iOS and their blogs on Weibo. It makes no sense. There are only a few of them who can publish books like tang Qiao. You can see what other scattered knowledge points can do. For beginners like me, the most important thing is to read books to sort out their iOS-related knowledge structures. Then, when I encounter a certain section, I feel that the book is not rich, go to relevant blogs Based on the topic knowledge. In this way, after your knowledge structure is established, you can read various blogs for a short time. You will have a good situation to accept these scattered knowledge. Instead of being led by various scattered blogs. Remember, the so-called cool people just suffer a little more than you. They have already walked over the road before you. Don't be afraid, go ahead firmly!

 

2. Continuous combat capability.

Problem description: according to my records of my behavior over the past few days, it often happens that I have been using too much effort for a few days, resulting in inefficiency or even inefficiency in the next few days. In this case, I think many people will have it. This is not just a problem for beginners of iOS, but it should be a universal problem. In this way, if you study for a week with an unstable learning efficiency, the effect of learning for a week with a stable and continuous learning efficiency is better.

Solution: The body State determines the learning state. First of all, we must ensure the body is in a good state. There are many articles in this regard. I will emphasize that we must go to bed before unless we work overtime at night. Persistence can form a habit. Therefore, learning tasks must be arranged into a combination of strategies, rather than just how much they must learn in a rigid day. In this way, it is hard to continue, not to continue, and many things are hard to complete. The so-called policy combination sounds high-end. Simply put, you can set a minimum amount of learning for yourself each day, which is easy to complete. This will at least make your study habits continue. This is the most important thing. Not indulging in your own desires is the key to achieving many things, and curiosity is also a desire. How to analyze website log files

 

3. A lot of brains, less hands-on.

Problem description: iOS development is a hands-on discipline, and I have hardly tapped into the Code since the last hundred days. This is a very big problem. Of course it is related to preparing for an interview, but this is not the reason for not typing the code. Yes, it is an excuse. I often think of code, and I don't know what to think about. I want to practice it and be intercepted by my perfectionist. I always want to know what I want to learn. This is a big mistake. I don't know. Your code is your best practice. Instead of reading articles on best practices, I tried to repeat the code. Instead, I kept reading the code and gradually approached the best practices. In fact, there was no perfect best practice. Good best practices are also strategic groups, rather than a single dogma.

Solution: try to knock on the Code as much as possible, and then practice in the code. You can knock on the questions in the book, the example code in the book, and find a simple project to imitate and write a demo. Always, you can't stop your hands. You need to knock on the Code more. Of course, if you get an iOS job, you should read the company's Engineering Code carefully, and then learn to crack and change the bug. I haven't gone yet. I don't know yet. After I got started, I first had to familiarize myself with the company's project code, and then modify bugs and write new requirements. Besides work, you need to find something to write. At present, we still need to set up the knowledge structure first, so I am going to carefully read the classic books on iOS, then, the exercises and case code are selected. This method is a bit stupid. I will see if there is any better way later.