Skip to main content

How many lines of code is ideal for your program?

While looking at the refactoring project over on SednaX, I found myself writing up some quick little code analyzer classes designed to see whether or not a function should be refactored or not.

Looking at that chart, it shows FoxPro has some numbers like 35 single lines of code per function. Wow - that seems low but maybe not.

So tell me - what do you consider to be the ideal number of lines per code / function for readability, maintainability in your programs?




Take the Poll and let me know...


Comments

Anonymous said…
I must be insane and hard to work with. That's all I can think of.

I've picked up a contract working on a VFP project where there is one main VCX with a bunch of classes inside of it. There is another VFP programmer that checks this VCX and VCT in and out of VSS. We are both doing development on our own copies of this VCx at the same time. THis class has methods/functions are huge with hundreds of lines of code, that were already ther and need refactoring.

When we "merge" our changes, it ends up being me that has to redo my edits into his master copy of the VCX. (Beyond Compare takes care of merging the PRG based changes.)

I had refactored some of his mega functions so I could use a subsection of the code and it caused a minor problem when they had to rush all of our changes into production because of another emergency.

I recently suggested that we break the big VCX into a VCX per class to ease checkin/checkouts, version control, and development. The response was "Not ready to break up the vc*, we have enough trouble getting bugs out of what we do breaking into separate functions."

I must be insane and difficult to work with.
November 10, 2005 at 9:29 AM
Andrew MacNeill said…
not if you look at the results of the poll. Seems like most like the idea of fewer lines per piece.
November 11, 2005 at 5:09 PM
Post a Comment

Popular posts from this blog

Merry Christmas

Whether you celebrate now, have already celebrated your past holiday, are planning to, or not, I hope you find yourself surrounded by family and those you love during this holiday season and are able to remember fondly those who are not with you. We often find ourselves buried in work, or too distracted by other problems, to share and remember a few moments with those closest to us. So many of us are separated by huge distances, we often find it easier to focus on those who are out of arm's reach yet so easy to connect with online, instead of those who are right beside us. So do yourself a favour, put down the keyboard (stylus, mouse, etc) and spend that time. I know I will. Merry Christmas. Powered by ScribeFire .
4 comments
Read more

Who Wants To Be Logical? I Do! I Don't! (with Claude)

In my book, Towards Consciousness, I explore PET , a theory that attempts to explain consciousness and possibly how it might apply to AI. As part of the conversations with AI series, I've included this conversation with Claude.AI in which we were talking about something very different and yet the conversation redirected itself back to PET. For the record, there is no such thing as "Colfsity". A It's interesting to me that people want to proclaim their distinction from being rigid and unlike machines, yet they also complain that the "best" people keep a rigid schedule, regular routines and logic understanding of issues. That's a perceptive observation about a real tension in how people think about themselves and what they value. There does seem to be this paradox where rigidity is simultaneously rejected as "robotic" or inhuman, yet praised when it appears as discipline, consistency, or logical thinking. I think part of what's happening is t...
Post a Comment
Read more

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...
11 comments
Read more