2 ms·
Companies can't track costs that stem from systemic inefficiencies. Say your programmers still use CVS for version control and you want to convince management
by adrianN 6y ago
Companies can't track costs that stem from systemic inefficiencies.
Say your programmers still use CVS for version control and you want to convince management to switch to Git. The CVS server doesn't cost much, a git server wouldn't cost much either. There would be a large cost for changing all your tooling and processes that rely on the CVS model and in training your programmers to use the new system. Why would you do that? How do you quantify the benefits of atomic commits or simple branching?
- nix23 6y agoThat example is too simplistic, it's called legacy systems and not legacy software. If you upgrade your tool-chain you include git. Really no one is interested in upgrading 'just' git, make a package out of it (new compiler, new CI, new testing, new version controll..fuzz etc) call the project "sustainable nextgen tool-chain...short SuNeTuCha" and sell it to the management like that.
- collyw 6y ago> There would be a large cost for changing all your tooling and processes that rely on the CVS model and in training your programmers to use the new system. When git seems to be by far the most used system on the market these days, isn't training any new hires in CVS going to be at least as much of a problem? I used it in my first job in 2003 / 2004, but I can't remember how to use it now. Do companies with legacy code tend to keep staff around for longer?