By bonlebon
via www-128.ibm.com
Published: Dec 13 2006 / 17:26
You can compare code duplication to an accident waiting to happen, just waiting for someone to make a modification and forget to carry it over to the duplicated sources. The resulting setback can be significant or minor, but no matter the magnitude, duplication remains a source of trouble. In this article, IBM developer Steve McDuff suggests configuration-driven development as a possible cure.
-
Special Report: Google gives a peek at Chrome OS
-
Lot’s of new software for IIS, ASP.NET, AJAX and PHP this week
-
C++ Programming: Increment And Decrement Operator : prefix and postfix
-
Applied Modularity - Part 1
-
What do you do after you find a bug ?
-
The Application Delivery Spell Book: Detect Invisible (Application) Stalkers
Comments
ilazarte replied ago:
wooooow. I actually thought of a very similar thing that i'll be putting into use at my company. the difference is that i won't be restricting the system to java. basically, you need a common format to describe system-wide functionality whether its a typeless gui, or a strong typed application or database.
the reality is that this isn't "configuration-driven development", it's the beginnings of the next major abstraction.
Voters For This Link (9)
Voters Against This Link (0)