| progr. |
унаследованная программная система (A legacy software system is years of undocumented corner cases, bug fixes, codified procedures, all wrapped inside software. If you start from scratch you’ll miss things. There is no guarantee that you’ll end up in a better situation, just a different one. If you try to reimplement a large code base in a modern language it turns out that even getting your new code to give you the same answer as you had before is fraught with complexities, and that’s before you even get to the domain-specific corner cases, because of the way different languages implement things as basic as adding numbers together. You’ve yet to speak to anyone that’s been involved with a project to reimplement a large legacy code base from scratch that has anything good to say about the idea. Document, improve the build system, modernise the infrastructure around it. Write tests. But don’t throw it away. Just getting a modern build system on top of your legacy code base, getting it into a revision control system, writing tests. That’s months or years of work right there. But afterwards you’ll be left with something that you can build and test easily. Which is what you wanted.  medium.com Alex_Odeychuk) |
