All I see, All I say, All I am

Oct 08

[video]

Oct 07

[video]

[video]

Oct 05

Steve Jobs’s Patents - Interactive Feature - NYTimes.com -

This is pretty incredible

[video]

Oct 04

Cave Canem

Cave Canem

Oct 01

Exactly

Exactly

Sep 30

(via aertime)

[video]

Sep 29

Planet frying pan

Planet frying pan

Sep 28

[video]

Sep 25

[video]

Sep 22

[video]

Sep 21

[video]

Pretty up your Objective-C logs with __PRETTY_FUNCTION__

Just a quick tip.  When I run a project in XCode and see a bunch of unformatted comments pop up in my gdb console I cringe.  Those logs are NOT helpful, fun to look at, or dig through to see where the messages are coming from.

Something I like to do is log a message containing the __PRETTY_FUNCTION__ string right after a method gets fired.  This makes it easy to make a half assed ‘backtrace’ when you need to figure out where things are breaking.

Just use the following:

NSLog(@"%s", __PRETTY_FUNCTION__);

Something else I like to do is use the NSLogger project so I can filter log messages by severity.  Just use the same technique described above with a macro that calls NSLogger with the lowest priority and you’ve got pretty useful system for logging that is searchable and allows adjustment of noise.  Also NSLogger has bonjour integration so that’s quite nice for reading logs from a device that isn’t actually plugged into your dev machine.