<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Code Style on miqu.me</title><link>https://miqu.me/blog/categories/code-style/</link><description>Recent content in Code Style on miqu.me</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 17 Apr 2015 23:39:03 +0100</lastBuildDate><atom:link href="https://miqu.me/blog/categories/code-style/index.xml" rel="self" type="application/rss+xml"/><item><title>Adopting nullability annotations</title><link>https://miqu.me/blog/2015/04/17/adopting-nullability-annotations/</link><pubDate>Fri, 17 Apr 2015 23:39:03 +0100</pubDate><guid>https://miqu.me/blog/2015/04/17/adopting-nullability-annotations/</guid><description>&lt;p&gt;Apple introduced nullability annotations to Objective-C compiler from &lt;a href="https://developer.apple.com/swift/blog/?id=25"&gt;XCode 6.3&lt;/a&gt;. I was really surprised by this change, and welcomed it with open arms when I saw the release notes. My first thought was: Objective-C is learning from Swift! I want to share my 2 cents on this new annotation and what it means for more modern Objective-C code.&lt;/p&gt;</description></item><item><title>A tale of categories and extensions</title><link>https://miqu.me/blog/2014/12/20/a-tale-of-categories-and-extensions/</link><pubDate>Sat, 20 Dec 2014 21:37:17 +0000</pubDate><guid>https://miqu.me/blog/2014/12/20/a-tale-of-categories-and-extensions/</guid><description>&lt;p&gt;I’ve gradually been changing my code style favouring (&lt;em&gt;Obj-C&lt;/em&gt;) categories and (&lt;em&gt;Swift&lt;/em&gt;) extensions a lot more. I’ve been inspired by my other lover (&lt;em&gt;Ruby&lt;/em&gt;). Why? Readability and code organisation.&lt;/p&gt;</description></item></channel></rss>