Friday, July 21, 2017

Too Much Codez!!! WHY?!?!?

Why must some programmers place as much code into a single file as they can?  Seriously?  Is this some sort of challenge?  Is there some advantage unknown to me by shoving all of a program's code into a single file?

Really, I am not a huge fan of the MVC pattern.  It places, sometimes, arbitrary guidelines regarding what should be placed in the Model, the View and the Controller.  However, it is better that the SEIOF pattern!  (Shovel Everything Into One File)

In my opinion, a logical separation of interests is best and basic.  One file for the GUI, one or more files for the application or business logic and one or more containing global types, classes, utility code, etc...

Placing all that into one large bucket can be confusing.  Please...  If you are a programmer, please, please separate your code a little bit.  Help save the next programmer's sanity.

Oh...  And those long methods/functions/procedures...  While in college I was taught that a method, function, procedure, subroutine, what-have-you, should be less than a page of printed code.  While that isn't always possible, it is still a guideline that I try to observe, and firmly believe other programmers should as well.

Happy Friday!!!

No comments:

Post a Comment