Many people on the blog and consulted on my iOS development how to improve, after some thinking, I can think of some of the following improvements, I personally also through these methods to improve.
Read the Blog
In this era of fragmented reading, blogs have been overshadowed by Weibo. And I keep writing blogs, and I read a lot about my peers ' iOS development blogs. Blog posts are usually about 3000 words in length, and many iOS development knowledge requires at least this space to be fully explained. And blogs do not have long publishing times for books, so reading blogs has a very good effect on getting the latest iOS development knowledge.
I carefully organized the domestic more than 40 iOS Development Bloggers blog Address list: Https://github.com/tangqiaoboy/iOSBlogCN, I hope you can cultivate the habit of reading blog.
There are also many excellent iOS development blogs abroad, their overall quality is higher than the Chinese blog, the following are some of the recommended blog address list:
Blog Name |
Blog Address |
Objc.io |
http://www.objc.io/ |
Ray Wenderlich |
Http://www.raywenderlich.com |
IOS Developer Tips |
http://iosdevelopertips.com/ |
IOS Dev Weekly |
http://iosdevweekly.com/ |
Nshipster |
http://nshipster.com/ |
Bartosz Ciechanowski |
Http://ciechanowski.me |
Big Nerd Ranch Blog |
Http://blog.bignerdranch.com |
Nils Hayat |
http://nilsou.com/ |
In addition, use the Blog RSS aggregation tool (such as feedly:http://www.feedly.com/) to get a better blog reading experience. There are also many good blog reading tools on the phone (I use newsify). Using these tools wisely can also make full use of your debris time, such as on the subway and before you go to bed.
Reading
The content of the blog is usually only a detailed explanation of a knowledge point, and the book can be a systematic introduction to the entire knowledge tree. Compared to foreign countries, Chinese books are sold at a fairly inexpensive price, so this is actually a very cost-effective way to improve. We recommend that you read at least 1 high-quality iOS development books every year.
Last year's "iOS 7 programming pushing the Limits" and "Objective-c Advanced Programming: iOS and OS X multithreading and memory management" are good advanced readings. By the way, I am also writing an iOS advanced book, which should be available before the end of the year.
Watch WWDC Videos
Because of the rapid development of iOS, Apple brings us a lot of new knowledge every year. And for this knowledge, first-hand information is WWDC video.
Usually, a new iOS development knowledge will be in the first WWDC on the Apple public, and then about 3 months, there will be a domestic and foreign blog to introduce these knowledge, after six months or so, there will be foreign books to introduce these knowledge. So if you want to get to know the knowledge early, then only through the WWDC video.
Now every year the WWDC video will be gradually released during the meeting, the important video with English subtitles. Reading these videos will not only get the latest iOS development knowledge, but also improve your English listening skills.
Look at Apple's official documents
Apple's official documentation is quite exhaustive, and for unfamiliar APIs, reading official documents is also the most direct and effective way.
Apple's documents are large, suitable to choose some key to read, such as human-computer Interaction Guide is required to read, and other content can be encountered when the focus of resources to consult.
See the code for an open source project
We must have this feeling, many times with the text to explain half a day, rather than write a few lines of code come intuitive. Reading good open source project code, not only can learn the basic knowledge of iOS development itself, but also can learn the design patterns and other software architecture knowledge.
If the reader can participate in the development of open source projects, they can further improve their ability.
Write more code, think more
Knowledge accumulation can not be separated from practice and summary, I think iOS code volume if not more than 100,000 lines, is not known to be familiar with iOS development. Some students in the school, just do a few C + + 's big job, in the job resume inside write "proficient in C + +", it is really let people laugh and cry.
While writing more code, we should also be careful not to "reinvent the wheel", as far as possible to ensure that each write code can be reusable. In the code structure because the business needs to change, in a timely manner, while not leaving technical debt, we also need to think more about how to design the application architecture, to ensure that the flexible product needs to meet.
In the process of reconstructing and thinking many times, we will gradually accumulate a kind of problem "best practice" way, become their valuable experience.
More communication with peers
Sometimes it is difficult to solve the technical problems, and the peer of a few words of communication may make you enlightened. Other common technical problems are usually met before, a few simple instructions can let you find the right way to solve all of a sudden.
The communication between the domestic developers can be done through forums, microblogging, QQ group and other ways. In addition, the major companies sometimes run a technology salon, which is also a good opportunity to know peers.
Need to be particularly reminded that, and domestic developers to pay attention to the discussion of quality, some forums and QQ group discussion quality is very low, the question is to be obtained through simple Google, this community must be away from, to improve their communication efficiency.
In addition to the domestic technical community exchanges, it is recommended that readers can go to the stackoverflow:http://www.stackoverflow.com abroad to ask questions or answer questions.
Share
The ways to share it are: launch an open source project, write a technical blog, and report at a technical meeting. There are some challenges in these ways, but if you can make a bold attempt, there will be great gains.
Posted by Tang Qiao Jul 27th, IOS
Original article, copyright notice: Free Reprint-Non-commercial-non-derivative-retain attribution | Creative Commons by-nc-nd 3.0
Chinese IOS/MAC Development Blog List
This blog list will be constantly updated and maintained, if you have a recommended blog, please submit blog information here.
This blog list covers articles that support customized Google search, especially thanks to Jeoam for providing and helping with updates.
This blog list also provides a synchronized update of the OPML file (download OPML file), which can be imported into third-party tools such as feedly, especially thanks to lcepy for providing automatic conversion scripts. Here are the import tutorials.
Blog Address |
RSS Address |
Onev ' s Den |
Http://onevcat.com/atom.xml |
House of the Broken ship |
Http://beyondvincent.com/atom.xml |
Nshipster |
Http://nshipster.cn/feed.xml |
Limboy no net Left |
Http://feeds.feedburner.com/lzyy |
The technology blog of Tang Qiao |
Http://blog.devtang.com/atom.xml |
Lex Tang |
Http://lexrus.com/feed.xml |
Read Nancy's Blog |
Http://nianxi.net/feed.xml |
Xcode Dev |
Http://blog.xcodev.com/atom.xml |
Ted ' s homepage |
Http://wufawei.com/feed |
Txx ' s Blog |
Http://blog.t-xx.me/atom.xml |
Kevin Blog |
Http://zhowkev.in/rss |
Mao's egg-sore place |
Http://www.xiangwangfeng.com/atom.xml |
Blog of the Asian Qing |
Http://billwang1990.github.io/atom.xml |
Nonomori |
Http://nonomori.farbox.com/feed |
Liker |
Http://tang3w.com/atom.xml |
Wonderffee ' s Blog |
Http://wonderffee.github.io/atom.xml |
I ' m Tualatrix |
http://imtx.me/feed/latest/ |
Cocoabit |
Http://blog.cocoabit.com/atom.xml |
Nixzhu on scriptogr.am |
Http://nixzhu.me/feed |
The boy who won't boot |
Http://studentdeng.github.io/atom.xml |
Nico |
Http://blog.inico.me/atom.xml |
The technical litters of Ali |
Http://hufeng825.github.io/atom.xml |
Answer_huang |
http://answerhuang.duapp.com/index.php/feed/ |
Webfrogs |
http://blog.nswebfrog.com/feed/ |
Code Artisan Man |
Http://joeyio.com/atom.xml |
Lancy ' s Blog |
Http://gracelancy.com/atom.xml |
I ' m Allen |
Http://www.imallen.com/atom.xml |
Travis ' Blog |
Http://imi.im/feed |
Wang Zhongzhou's Technical Blog |
Http://wangzz.github.io/atom.xml |
Pigs that would write code |
http://gaosboy.com/feed/atom/ |
Wei's Blog |
Http://feed.cnblogs.com/blog/u/23857/rss |
Rock poet |
Http://feed.cnblogs.com/blog/u/35410/rss |
Luke ' s homepage |
http://geeklu.com/feed/ |
萧宸 Yu |
Http://iiiyu.com/atom.xml |
Yuan Blog |
Http://www.heyuan110.com/?feed=rss2 |
Shining IO |
Http://shiningio.com/atom.xml |
yifeiyang--Easy-Flying Blog |
Http://www.yifeiyang.net/feed |
Koofrank ' s Blog |
Http://koofrank.com/rss |
Hello it works |
Http://helloitworks.com/feed |
Code Farm Life |
Http://msching.github.io/atom.xml |
Jade makes the world's blog |
Http://yulingtianxia.com/atom.xml |
A bear who does not dig a honeycomb |
Http://www.hotobear.com/?feed=rss2 |
Cat and Rinpoche |
Https://andelf.github.io/atom.xml |
Stewed rice |
Http://ivoryxiong.org/feed.xml |
The development of Tenderloin string |
Http://adad184.com/atom.xml |
Chun Tips |
Http://chun.tips/atom.xml |
Why ' s blog-Wanghai's lab |
Http://blog.callmewhy.com/atom.xml |
Kenshin Cui ' s Blog |
Http://www.cnblogs.com/kenshincui/rss |
Blog of Technology Brother |
http://suenblog.duapp.com/rss/ |
How iOS Development improves