4 ms·

But when you do need it, and you haven't put in the mechanisms to replace it. Your screwed. Without the proper abstractions things can become tightly coupled,

• crdoconnor 9y ago
  You can go overboard though. Excessively loose coupling can come at the expense of DRY (and vice versa). It's a trade off.
• lgas 9y ago
  The problem is that few projects survive long enough to get to the point where anyone can be annoyed by the lack of foresight... so often any foresight or effort on implementing what was foreseen is wasted effort. Often times that wasted effort contributes to the premature death of the project by soaking up resources that could've been used to implement more features, fix more bugs, etc. The question is which is more problematic, the lack of foreseeing the need to change the database or the lack of foreseeing the death of the project due to spending time on the wrong things? Personally I think having a successful project that needs the database changed is a) not a particularly hard problem to deal with and b) a good problem to have.