Timeline for Why develop internal libraries for internal applications?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 25, 2017 at 21:03 | comment | added | Michael Borgwardt | @Sirisian: I added a paragraph about that. | |
| Aug 25, 2017 at 21:03 | history | edited | Michael Borgwardt | CC BY-SA 3.0 | added 665 characters in body |
| Aug 25, 2017 at 20:39 | comment | added | Laiv | Think also in maintenance. 1) The lib can be maintained independently and in parallel. 2) Is code easy to replace. 3) Small code base are easier to manage for small teams and easier to understand for everybody. 4) if time-to-market is critical, you will prefer to have faster builds. Code in libs is code you don't compile over and over in the pipeline (IMO). 5) It's reliable reusable code... You made It ;-) | |
| Aug 25, 2017 at 20:28 | comment | added | Sirisian | Nearly every VCS for the past decade supports external references or submodules. This removed the duplicate code and bugfix problem. Might include more information on why these aren't a viable solution if you still believe they're valid problems. | |
| Aug 25, 2017 at 20:21 | vote | accept | AndyM | ||
| Aug 25, 2017 at 21:43 | |||||
| Aug 25, 2017 at 20:21 | comment | added | AndyM | I believe that may be possible through shared libraries. Thanks for clarifying, I'll mark your answer as accepted. | |
| Aug 25, 2017 at 20:09 | comment | added | Michael Borgwardt | @AndrewMurtagh: Yes, that's pretty exactly how I'd put it. Although there may be technical reasons too; I'm not that familiar with C/C++ development - maybe keeping part of the code as a library is necessary so it can be loaded optionally or even loaded and unloaded on demand, and thus reduce memory usage when the fuctionality is not needed? | |
| Aug 25, 2017 at 20:02 | comment | added | AndyM | So as I understand, the main reason to make some piece of code into a library is when it is going to be used across different projects (even if they are all internally developed) in order for that code not to be duplicated, updated, maintained separately? And if you are only going to be developing a single project then there is no need to make something into a library (unless you intend on using it in further projects at a later date). | |
| Aug 25, 2017 at 19:54 | history | answered | Michael Borgwardt | CC BY-SA 3.0 |