Timeline for Are there any significant disadvantages to depending upon abstractions?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 1, 2015 at 7:54 | comment | added | Marjan Venema | Obligatory statement: "Yagni is only a viable strategy if the code is easy to change" | |
| Nov 11, 2015 at 19:09 | comment | added | Spotted | @Fuhrmanator You are right, the example I gave is rather esoteric. But since the OP wanted to know if we should in all cases depend upon abstractions, I just wanted to give an example when not. :) Aside this, I think abstraction is a powerful tool for a programmer (but as for every tool, it must be used for the right job). | |
| Nov 11, 2015 at 19:03 | comment | added | Fuhrmanator | @Spotted No problem about not being able to patch. It's just a pretty specific example and not typical of most software. | |
| Nov 11, 2015 at 19:02 | comment | added | Fuhrmanator | @Eilon my comment was about modularity is not always needed (not abstractions). | |
| Nov 11, 2015 at 18:50 | comment | added | Spotted | @Fuhrmanator Of course we have common code in libraries, but as Eilon said, not everything depends on abstractions (some parts do, however). I never said there never are bugs, I said they can't be patched (for reasons that are outside the scope of the OP's question). | |
| Nov 11, 2015 at 17:34 | comment | added | Eilon | @Fuhrmanator common code is different from abstractions. Common code can just mean a helper method or library - no abstractions are needed. | |
| Nov 11, 2015 at 14:46 | comment | added | Fuhrmanator | I tend to agree with YAGNI, but I wonder about your example. Are you never repeating any code in the different devices? I find it hard to believe that there isn't some common code across the devices from the same company. Also, how do clients like when you don't fix bugs in their firmware? Are you saying there never are bugs, ever? If you have the same code that's buggy in 4 different implementations, you have to fix the bug 4 times if it's not in a common module. | |
| Nov 10, 2015 at 21:11 | history | answered | Spotted | CC BY-SA 3.0 |