In practice I find I'm a terrible judge at where the function boundaries should be. Several times I've tried to reorganize a project where functions had gotten gradually too big, ended up making them too small and numerous and having a pain debugging, then finally settling on some intermediate position. All the overly-certain talk of "as many functions as you need" misses these nuances.
(I wrote recently about global vs local readability: http://akkartik.name/blog/readable-bad)
So, you think it that code should be measure by the size of the code?
a = b + c; is better than the other?
Care to explain why?
I meant that everytime somebody refers to the value of controlling code size (like gruseom did in this thread), we have to deal with the inevitable strawman of:
int a = b + c;
int hours = timesPerformed + hoursPerPeformance;
(PG has also said this many many times with reference to arc.)