If I were a dog, what sort of dog would I be?

I’d certainly be a dog.  What a life.  Eat, sleep, run around, no programming required.  I’d have to battle the occasional worms problem, hopefully my owners would spend the outrageous money to get me medicine, but, all in all, not a bad life.  A house cat would probably be even better.  At least I wouldn’t wake up with a stuffy head after grooming myself.  And this relates to programming how?  Well, in a nutshell (no, we’re not talking about squirrels now, though have you seen one lately, they’re HUGE) programming is like choosing to be a type of dog.  There is a programming language to be chosen as well as a programming style.  For most programmers, they have a pet style and pet language.  For us at DDA, we’ve been using the programming language Coldfusion, as we are a website-based program, and our programming style has evolved over time, though it much depends on the programmer.

Yesterday, Elizabeth floated some ideas for those of us having trouble finding topics to write about.  Her question to the programmers is what is module programming, modular programming, and what is the difference between the two.  I thought about this for a while, and though most of this has more to do with some of the static programming concepts, not web-based languages, in a way we work with it as well.  Modular programming is a programming style that in my opinion was formed out of the great need for many programmers to work on single projects, as well as creating programs that can multitask rather than running from point A to point B, linearly.  Its basis is that a programmer should be able to create a module (module programming) that can be easily plugged into any part of a program given the right information.  It lends to code reuse, easier debugging, and a general slimming down of code that has to be written and rewritten.  It is made for programs that do not necessarily have a beginning and end.

The DDA Pulse project, which is the neverending intranet system we’ve been working on for some time now is modularly programmed.  We have a main function, a login system, and then every other piece of the program is a self contained system that only requires a few things to be passed through for security and function, and everything runs inside that.  It comes pretty close to object-oriented programming as I think web scripting can, without relying on a huge framework.  I’ve been very pleased with what we are able to so far do with modular programming, and would like to continue on that path as it makes for quicker development, and we can have several of us working on a web project at a time.