Suggestions on iOS development learning path
A friend in the iOS Forum asked to answer the post. The post title is:To learn more about IOS development, start fromAnd then I wrote a lot of answers. Since I typed so many words, I posted my replies to my blog to share them, hoping to help you. Welcome to discuss and share in the post, address: http://bbs.csdn.net/topics/390920759
The following is my reply:
Let's talk about iOS learning suggestions based on our own situation. Here we will not talk about the principle, but how to do it. You are welcome to make a brick
1. The first requirement is that you can read the official documents smoothly.
If you have difficulty reading official documents, you can talk about how to improve and improve. the materials we use to learn about iOS ownership come from the apple developer website, viewing posts through forums is not the way out. If this is not met, read the official document and find an official document on the technology you are familiar with, for example: View Programming Guide for iOS read, translate, and write down words that you don't understand. Learn them several times more, in the future, when you read other documents, there will be countless times. After a few months, you will find that English documents look better than Chinese. Why do you need to look at the technology you are familiar with? In that case, you are more likely to understand and increase confidence.
English learning is a long-term process, I recommend a good article, specifically teach you how to learn and improve English: Old Code agricultural teach you to learn English http://blog.jobbole.com/45296?
2. Learn some official technical guides. There are various documents in Apple dev. We recommend that you start with some guides to systematically learn the knowledge of a certain module.
For example, if you want to learn AutoLayout systematically, you can check it out. Auto Layout Guide
Here are the home pages of various technical module guides:
Https://developer.apple.com/library/ios/navigation/#section=Resource%20Types&topic=Guides?
3. WWDC video materials Are you tired of reading the technical documents of text documents? Don't be afraid. Apple is a user-friendly company. They hold WWDC every year. Apple's technical experts will explain new technologies and some technical topics in the classroom.
There are video available for learning: https://developer.apple.com/devcenter/ios/index.action can be found here.
There are too many video themes. You only need to select the theme you want to learn. What should I do if all officially provided videos do not contain subtitles?
To everyone a very good website, it has been the recent years WWDC of various classroom speeches are organized into a text version: http://asciiwwdc.com/, rest assured that the text version is certainly English.
4. Follow up and add some iOS personal blogs that suit your appetite and start to write your own technical blogs. Why is it suitable for your appetite? In reality, after all, there are still a few masters, and the majority of scammers.
The blog you are paying attention to is too high-level and beyond the scope of your understanding and ability, it will only make you feel inferior. I always feel that I can't take anything I write.
When you go to school, you cannot learn how to learn Overlord. When you get to work, you can only look up to learn Overlord's blog.
The right appetite is that the article seems understandable and can be converted into its own things.
Lin yuanyu, it is better to leave the web. Start blogging now.
We recommend two articles to share with you.
As a technician why write blog http://blog.jobbole.com/48962?
Do you want to write a blog even if you have no readers? Http://blog.jobbole.com/38258?
5. Read the source code of an excellent iOS open-source project. Sometimes I don't know how to improve the code I wrote. I think reading excellent open-source projects is a good choice.
There are countless outstanding open-source iOS projects. Find an open-source project that you are familiar with, analyze and write a blog.
Think about the design patterns used in open-source projects, the APIs used, and how to apply them to your actual projects.
6. Write and submit your own open-source projects Now you are starting to focus on several open-source projects on Github, as well as the number of star and Fork. These are more valuable than resumes.
Github projects are more accurate than resumes. You can see the quality and record of code submitted by the project on Github.
The benefits of Self-writing open-source projects are self-evident. You can improve your skills and increase your weight for future job hopping.
I have said so much about my own situation. The first four articles above are already in practice and can be used flexibly. 5. Six items are being put into practice and are not finished yet.
However, this is also my learning direction, and I will share it with you.
