3 ms·
If you have proper functional tests, you can replace wrong abstractions at a cost. The real issue is code abstracted bottom-up instead of proper design. Such a
by AstralStorm 10y ago
If you have proper functional tests, you can replace wrong abstractions at a cost.
The real issue is code abstracted bottom-up instead of proper design. Such abstractions end up being special cases and become annoying and worthless if requirements (incl. internal ones) change.
While sometimes you can design yourself into a bad end (typically by not taking a really critical requirement into consideration), this is not what often happens.
- sodapopcan 10y ago> The real issue is code abstracted bottom-up instead of proper design. Exactly. We're (basically) saying the same thing here. I kept my comment short-and-sweet as not to get into the nitty-gritty of everyone's different work situations/requirements/stances on different testing practices/building an app vs a library or service/programming paradigm/etc. To expand ever so slightly: "These days I'm all about 'dirty integration' first to help inform my ultimate design."