Timeline for Logistics of code reuse (OOP)
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 24, 2011 at 11:36 | vote | accept | Ominus | ||
| Jun 23, 2011 at 15:25 | comment | added | Jim C | Documentation is the key. Even you will forget what you coded 6 months ago. If it is not documented, it might as well not exist. | |
| Jun 23, 2011 at 15:00 | comment | added | FrustratedWithFormsDesigner | @Ant: Often happens in massive (and usually well-aged) projects where the time to find the earlier implementation is perceived as being longer than just implementing a new one. This may be exacerbated by documentation that is inadequate by either omitting these features or by being so huge and overwhelming that most people just read the first few pages and look at the high-level diagrams because searching the documentation is almost as time-consuming as searching the codebase. | |
| Jun 23, 2011 at 14:57 | comment | added | Ant | @Karl Bielefeldt: Yikes, that's not just Not Invented Here; it's Not Invented Here In The Last Five Minutes (NIHITLFM). | |
| Jun 23, 2011 at 14:47 | comment | added | Karl Bielefeldt | +1 for the discoverability comment. At my last count, our code base has 7 nearly identical implementations of zlib decompression. | |
| Jun 23, 2011 at 14:42 | history | edited | Michael K | CC BY-SA 3.0 | added 1 characters in body |
| Jun 23, 2011 at 14:19 | comment | added | Ominus | Fixed the question so it refers to classes now. | |
| Jun 23, 2011 at 14:15 | history | answered | FrustratedWithFormsDesigner | CC BY-SA 3.0 |