I actually have a blog post about this general subject: http://jasonmbaker.com/the-devils-in-the-details http://jasonmbaker.com/the-devils-in-the-details In e

I actually have a blog post about this general subject: http://jasonmbaker.com/the-devils-in-the-details http://jasonmbaker.com/the-devils-in-the-details In extracting code into a method, you're intentionally obscuring what it does. Most of the time this is a good thing because you want to only focus on the details of the routine you're in. Thus, if you follow the "make your method do one thing" rule, you should be ok. If your methods have no cohesion to them, then you will have problems breaking them down. But then again, I would argue that that's the least of your problems.