News for hackers. Stuff that matters.
Re:Avoid DRY for Product Development by terra_t on Sunday November 21, 2010 @06:11PM (#1928163)
Damn... I had a boss that wrote significant parts of a product and we could always tell that he wrote part of it because he'd repeat a 30-line block of code 7 times, rather than writing a subroutine.

There are cases where we all violate the DRY principle... Sometimes it makes sense to subroutinize something the fourth or fifth time rather than the second time. But overall, DRY is good.

Re:Avoid DRY for Product Development by mathgladiator on Sunday November 21, 2010 @06:40PM (#1928232)
I think DRY is very good, and I feel like many people missed the point of what I wrote.

DRY is very engineering centric which works very well for systems (i.e. non visual things like MySQL or node.js).