Friday, May 05, 2006

Procedural is for the army

Okay, don't get me wrong, but procedural code has its place. Inside a little box far away from enterprise solutions. It is great for the quick fix it or the once off or twice off export.

The reason I say this is because developers come and go but the application running your enterprise will be around for a long, long time. Now if you write this solution in procedural code making changes is a NIGHTMARE! If you change one line of code the implications bubble through all 1000 lines of your web page!

Now take Object Orientated design and you have a scalabile, updatable model. It might take longer to design and impliment but at the end of the day are you looking for a quick fix or a long term solution?

Every developer has different ways of developing procedual and object orientated code BUT the object orientated code (if designed properly) has more advantage is the long run. It makes finding procedures easier, updating the procedure shouldn't affect the objects that hook into it (unless it is exposed and used by other classes). What a pleasure!

Anyways, you take the high road and I'll take the low road and have less maintenance to do, which means I get home before you! :P

Enjoy your weekend people.

No comments:

Post a Comment