The author of the Thinking In Java series, Bruce Eckel, wrote on his blog about the problem of misconducted code reuse in development, and the resulting 'framework-itis' dilemma. He quoted,
"Framework-itis in general is one way, and probably the most highly-criticized way, that attempts to reuse code go bad.""I postulate that most of the corruption in code resue comes when someone decides ahead of time that we should reuse code. That is, when it is driven by perception rather than need. I have personally found reusable code at the point when I need it a second time, as a process of discovery. And usually it's something I can't anticipate, or at least don't anticipate it in exactly the way that I need it."
Read the whole article in his blog here.
0 comments:
Post a Comment