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...


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.
Andrew MacNeill said…
not if you look at the results of the poll. Seems like most like the idea of fewer lines per piece.

Popular posts from this blog

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 distinctions I…

Security in Windows 10

 discusses some Windows 10 privacy settings and their implications.

"Finally, we will access, disclose and preserve personal data, including your content (such as the content of your emails, other private communications or files in private folders), when we have a good faith belief that doing so is necessary." "In other words, Microsoft won't treat your local data with any more privacy than it treats your data on its servers and may upload your local data to its servers arbitrarily"
I did a quick install on a VM choosing the Express settings. When I fully deploy this on a real workstation, I will likely choose to wade through all of the individual pages, as David recommends.

Of course, losing one's privacy is nothing new - it's happening all over the place (despite Santa Ana's police force's lawsu…


I'm not TRYING to be "fanboy-flame bait" but what I saw yesterday was a typical "Do it this way, now do it this way and then we'll go back to this way" all over again.... a move similar to what Microsoft does to developers on an ongoing basis.

Remember the first iPhone? Smooth and curved, at least as far as it could be back then. I still pull out my 3G and can see the curves on it.

Then the 4 came out and "boxy" was all the rage. Everything should be "tight with corners"

Now iPhone 6.... smooth and curvy is back. Granted I don't have the actual device yet, but that's the message.

Guess that means the iPhone 8 will be back to boxy.

And honestly, Apple Watch is not worth "one more thing" --- especially when everyone knows it's going to be shown. "One more thing" would be something no one saw coming.  The device itself ? Very interesting and yes, definitely lots of potential but "one more thing" wor…