<story><title>Behind enemy lines: 3 months as an iOS developer at Google</title><url>http://www.splinter.com.au/2012/12/26/behind-enemy-lines-google/</url></story><parent_chain></parent_chain><comment><author>gdubs</author><text>I&apos;ve had to resolve merge conflicts with pbxproj files and xib files, and while it&apos;s not pretty, it&apos;s not a good enough reason to eschew interface builder. There&apos;s a reason that toolset is still around since the NeXTStep days: it&apos;s powerful. It gets a lot of giggles from people who are less experienced with Cocoa / iOS, and think that programmatically defined UI is for &apos;real&apos; coders. In my experience, the amount of time you save wiring-up an app with interface builder is significant. With the editor assistant screen open, you can even drag UI element outlets directly to your code, and it will automatically insert your property declarations (and same with method actions). The idea that I&apos;m going to grok someone else&apos;s UI code at a glance -- the same way I would looking at a visual document -- is absurd. Does interface builder fit every situation? Absolutely not. But for the vast majority of apps, you&apos;ll get your rapid prototype finished more quickly if you use the tools, and then you can tweak from there.</text></comment>
<story><title>Behind enemy lines: 3 months as an iOS developer at Google</title><url>http://www.splinter.com.au/2012/12/26/behind-enemy-lines-google/</url></story><parent_chain></parent_chain><comment><author>davidjgraph</author><text>Am I the only one thinking that this contract was probably bound under an NDA, and that making such a post is generally bad practice leaving employment/a contract (regardless of whether there&apos;s an NDA).&lt;p&gt;I know nothing ultra-secret is given away, but if I were looking for a contractor, I&apos;d be concerned that such a person might perform a post-mortem on my company after leaving as well.</text></comment>