Casey's compression oriented programming advices that code that is written multiple times should be reformatted into a function, but sometimes i get functions that are too big for me to look at, without having the privilege of obviously rewritten code.
My criterion for too big of a function is one that i can't reason with myself exactly what it does without looking at it, or that it has a lot of parts that all of them is related to one aspect of my software, and none of them seems to obviously not connected to the others enough to take them out to a different function.
What can you do in this situation? Should you just break them out? what if there's a better way of organizing that code that can only be viewed if looke together?