A design problem I met again and again.

[Lawrence D'Oliveiro]

In message <158986a9-b2d2-413e-9ca0-
c584299f176b at f1g2000prb.googlegroups.com>, 一首诗 wrote:

> On Apr 1, 4:55 pm, Lawrence D'Oliveiro <l... at geek-
> central.gen.new_zealand> wrote:
>
>> In message <48506803-a6b9-432b-acef-
>>
>> b75f76e90... at v23g2000pro.googlegroups.com>, 一首诗 wrote:
>> > Until one day I find service has nearly 100 methods and 6000 lines of
>> > code.   I don't need to read any programming book to know that it's
>> > too big.
>>
>> The question is not how many lines or how many methods, but whether it
>> makes sense to remain as one piece or not. In one previous project, I had
>> one source file with nearly 15,000 lines in it. Did it make sense to
>> split that up? Not really.
> 
> What are the average size of source files in your project?   If it's
> far lower than 15,000,  don't feel it's a little unbalance?

Why?