Timeline for The importance of duplicate code removal
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 16, 2014 at 13:44 | comment | added | BrianH | I've always found better luck on putting it on people who aren't present or who preferably don't exist: oh sure, you're a good programmer, but some people aren't! And a bug any lesser being might create because he didn't pay really close attention to your code is still a problem. This can, at times, make things a little less personal. | |
| Sep 16, 2014 at 13:11 | comment | added | Brandon | This is why I believe that every developer should be in a position to maintain their own work. Seeing what goes wrong teaches you what not to do. | |
| Sep 16, 2014 at 12:27 | vote | accept | Iulian Onofrei | ||
| Sep 16, 2014 at 10:01 | comment | added | Iulian Onofrei |
Very interesting and complete answer. The What's not to like? part is the exact thing that he was expressing. And, sadly, the attacking you were talking in the last paragraph is exactly what I did, but I didn't have enough proof of it.
|
|
| Sep 16, 2014 at 9:48 | history | answered | Kilian Foth | CC BY-SA 3.0 |