coding convention for length of method / class
Since the project I'm working on is the largest project I have ever done (it is for my dissertation), I have often revisited sections of code or analyses where I ask myself "what the hell was I doing here?" after months at at time.
So, to help alleviate this stress, I decided to finally write some code which gives me useful statistics on my own coding habits, like average function length, file size, and so on.
I have heard conventions on this before, but never bothered to follow them when I was knee deep in code because I wanted to flush the ideas out. Any advice on the topic?
For the record, there are 25848 lines of code as of today (I've been working on this project for four years), and that is from 58 source files. Not including the matlab I've done on the side... and it's giving me a headache.
It turns out the function lengths, in terms of lines, follow a long-tail distribution, just like a lot of other stuff in language like word frequency... at least from my sample, and the sample in the java code in my "program files" directory.