static const NSTimeInterval NYTArticleViewControllerNavigationFadeAnimationDuration = 0.3;
applicationDidLoad:withANotification:iWonderWhatTheWeatherTodayIs:LetsAskSiri:That's the whole point of it ;-). Remember you usually only have to write the code once, but you or someone else may have to read it many times.
I used to hate long variable and function names in the past, and I used to hate named parameters. Going on the assumption the time spent typing the code was somehow relevant, and also feeling a little more badass being able to write all this cryptic gibberish to 'control the computer'. In time, I've learned none of this matters and readability of your code is one of the most important quality metrics of any piece of software that needs to be maintained by multiple people and/or over a long timespan.
It even fails to complete types like NSString correctly when part of a method call. Not always of course, just when it gets confused, and then I have to delete and type again because the case is wrong.
My only gripe about developing on a 13" MBP is not being able to have 2 buffers side by side without wrapping the snot out of half the lines.