title: Does coding many small methods have performance ramifications for Objective-C?
body: <p>I come from Ruby, and have sort of adopted the methodology of single responsibility principle, encapsulation, loose coupling, small testable methods, etc., so my code tends to jump from method to method frequently. That's the way I am used to working in the Ruby world.  I argue that this is the best way to work, mainly for BDD, as once you start having "large" methods that do multiple things, it becomes very difficult to test.</p>
  
  <p>I am wondering if there are any draw backs to this approach as far as noticeable differences in performance?</p>