Does it make sense to keep two different versions of code?
I am developing projects for my private use and have been wondering how I should design my projects. I always try to keep the code as efficient and concise as possible and as readable as possible. However, I still find it difficult to balance both sides and wonder, how professionals set up their projects. Personally, I can imagine where writing and keeping two software codes makes sense. For example, one wants to have a test version that simply implements all the desired functionality and use that one as the base-line and test system. The second version of the code can then be the version that is performance critical, but still has to contain all features that exist in the first software version. This is however purely my thought and might not be how it's done in the industry. I can imagine well, that above's procedure is simply not applicable, because everything now costs twice the time and time is money.
I am developing projects for my private use and have been wondering how I should design my projects. I always try to keep the code as efficient and concise as possible and as readable as possible. However, I still find it difficult to balance both sides and wonder, how professionals set up their projects.
Personally, I can imagine where writing and keeping two software codes makes sense. For example, one wants to have a test version that simply implements all the desired functionality and use that one as the base-line and test system. The second version of the code can then be the version that is performance critical, but still has to contain all features that exist in the first software version. This is however purely my thought and might not be how it's done in the industry. I can imagine well, that above's procedure is simply not applicable, because everything now costs twice the time and time is money.
What's Your Reaction?