News for hackers. Stuff that matters.
Re:Attitudes That Lead to Maintainable Code by sodapopcan on Wednesday March 08, 2017 @10:01AM (#13820649)
Yeah, this really reminds me of Sandi Metz's "Duplication is less expensive than the wrong abstraction." I know we aren't talking duplication specifically here, but I've eagerly built the wrong abstraction several times and it suuuuucks.

These days I'm all for the "dirty integration" first.

Re:Attitudes That Lead to Maintainable Code by AstralStorm on Thursday March 09, 2017 @06:38AM (#13828620)
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.

Re:Attitudes That Lead to Maintainable Code by sodapopcan on Thursday March 09, 2017 @11:32AM (#13830353)
> 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."