Has it ever happened to you that you take a simple 6 hrs task, build it and then redesign to make it generic by wasting 30 hrs more and spend another 20 hrs documenting it so that others can use that generic feature?

  • 0
    YAGNI is a tough learning process..

    its not always easy to write code that solves only a current problem. with no foreseen future features and stuff. it can still be elegant, when its written "solid" enough that it COULD be refactored to be generic, should it once become REQUIRED
  • 1
    General code is not a happenstance of normal coding (especially object oriented) so it needs a lot of careful planning and a hefty dose of over engeenering to be usable and reliable.
Add Comment