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.
-
The story of the mysterious WINA20.386 file
-
PHP 5.4 Traits, Closures, and Prototype-based Programming
-
Spring Data JPA 1.1.0 RC1 and 1.0.3 GA released | SpringSource.org
-
I’m a 17 year old developer up against a 19 year old, his company and a $1.1M investment
-
Send me a patch for that
-
Forms and Crud with PHPDevShell
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)