News for hackers. Stuff that matters.
Re:Why bad scientific code beats code following “best practi... by sbov on Sunday August 28, 2016 @02:52PM (#12377870)
You also have to factor in the cost to maintain your extension which you currently have no use for, which most people forget.

It also might be easy to include now, but your extension might complicate a new feature request. Or the new feature might complicate your previously simple extension. If it's still unused, don't be afraid to throw it away then either.

Re:Why bad scientific code beats code following “best practi... by Gibbon1 on Sunday August 28, 2016 @03:43PM (#12378136)
I find that unneeded functionality also complicates refactoring efforts.