Audio podcasts are my favorite way to squeeze in a little entertainment or information while performing other tasks. While I'm driving. When I'm at the store. I almost always have my Earpods in and a couple episodes downloaded and queued up in my player.

There are a lot of different ways to build a universal application for iOS and every project is different. By leveraging auto layout, storyboards and custom UIView subclasses you can save time and avoid unnecessary duplication.

A Developing Story is now The Main Thread. A more suitable name for where I update my interface to the internet at large.

Having spent close to a week with Google's best-yet foray into TV-land I decide to post my thoughts on what's good and not-so-good about this "dongle".

I often forget about NSScanner. Maybe because I've spent so much time working in languages where there's no analog. In this, the first (and so far only) installment of Real Code™, I share a function I wrote recently to parse KML coordinate sets.

When working with Objective C you may come across a situation where using a placeholder object can save you complexity when an actual instance is not available or required. By using protocols you can retain type-safety while defining objects that behave like instances of other classes.

Taking screenshots on your iOS devices is something I imagine all developers (and designers) have to do regularly. The addition of Photostream made this easier but I was really getting tired of opening iPhoto each time I wanted to pull a screenshot into Photoshop. Turns our there's a better way. A few actually.

I honestly wasn't sure it would happen but App.net is actually starting to get interesting. Not for the core Twitter-like experience. But for what developers are building on the foundation of its APIs

Dispensr is a better way to distribute multiple promotional codes for iOS and Mac software. You just upload the file you receive from iTunes Connect and you get a single, private url to share via email or on Facebook, Twitter or App.net. Your users get to request a code without trying multiple times only to find out that they've all been used.

Now that I have a few more months experience using auto layout in Rego I'd like to follow up my original post with some additional thoughts on the technology, how one might use it, and what can, and will, go wrong.