On DRY and the cost of wrongful abstractions

Re:On DRY and the cost of wrongful abstractions by mozumder on Sunday September 18, 2016 @06:28PM (#12527536)

I'm firmly in the anti-DRY camp since it causes everything to be slow, including coding speeds. You spend far too much time trying to figure out something new, when you could have just cut-and-pasted the answer from the previous problem.

Repeat yourself. It's good for you, and makes you code faster.

You can refactor out later if code becomes bloated.

[ Parent | on HN ]

Re:On DRY and the cost of wrongful abstractions by meddlepal on Sunday September 18, 2016 @07:10PM (#12527674)

And then one day you realize there are bugs duplicated all over the place and you pray that nobody hits them.

I'm not religious about DRY, but it's not a bad thing when kept in the toolbox with KISS and YAGNI.

[ Parent | on HN ]

Re:On DRY and the cost of wrongful abstractions by mozumder on Sunday September 18, 2016 @08:09PM (#12527897)

> And then one day you realize there are bugs duplicated all over the place and you pray that nobody hits them.

If you can copy-paste repeated code, you can copy-paste debugging as well.

Duplicate bugs are a single bug.

Obviously not all DRY is bad.

[ Parent | on HN ]

Re:On DRY and the cost of wrongful abstractions by meddlepal on Sunday September 18, 2016 @08:41PM (#12528031)

And then I can explain to my boss why I'm working on stuff I'm not supposed to when I could have just wrapped it up once in a library and fixed it once on all those projects.

So now not only have I created a bug, duplicated it N times, but my boss thinks I'm an idiot and wasting time for not applying DRY and good engineering hygiene.

[ Parent | on HN ]

Re:On DRY and the cost of wrongful abstractions by rsyntax on Monday September 19, 2016 @08:12PM (#12535869)

> Repeat yourself. It's good for you, and makes you code faster.

Maintainable goes out the window...

[ Parent | on HN ]