<p>Interesting story how a development team at Facebook <a href="https://code.facebook.com/posts/313033472212144/debugging-file-corruption-on-ios/">debugged a resource handling issue</a> in their iOS app.</p>

<p><a href="http://blog.regehr.org/archives/199">A</a> <a href="http://blog.regehr.org/archives/208">couple</a> of interesting articles about debugging. Debugging doesn’t seem to get a lot of attention when people are taught about programming, I assume you’re supposed to acquire this skill by osmosis, but it is actually one of those skills that should receive much greater attention because it’s one of those that separates highly productive developers from, well, not so…

<p>OK, I admit it - I’m a dinosaur. I still use the command line a lot as I’m subscribing to the belief that I can often type faster than I can move my hand off the keyboard to the mouse, click, and move my hand back. Plus, I grew up in an era when the command line was what you got when you turned on the computer, and Windows 2.0 or <a href="http://en.wikipedia.org/wiki/Graphical_Environment_Manager">GEM</a> was a big improvement.</p>

<p>First, a confession - I actually occasionally call myself a coder, but in a tongue in cheek, post-modern and ironic way. Heck, it does make for a good blog title and license plate.</p>

<p>Like pretty much every other programmer with a Mac, I’m currently looking at <a href="https://developer.apple.com/swift/">Swift</a>. Will I write anything but toy programs in it? I don’t know yet - I don’t really write any Mac-ish software on my Mac,  just unix-ish programs. If Swift doesn’t escape the OS X and iOS ecosystems it’ll be a nice exercise in a neat language that’s not really that relevant to the world at large, or at least to my part of the…