The cost of not using version control

General News

Summary

Last week we published a blog post my colleague Hannah wrote on our library development process. The process included the use of version control to manage regular library revision backups and also merging of multiple user developments into one central repository. If you named and commented each revision appropriately it will be easy to choose how far back to rewind the library version. On average I would estimate 3 hours of work to find the manually backed up snapshot of the model library that gives you results that are good again and understand exactly what changed. Let’s not bring in the amount of time that is also required to manually retest all experiments affected by the model changes unless you can bear to even think of that.

Classifications

industries
No industries detected
applications
Engineering & Scientific

AskAI Classifications

Labels
Simulation Software Modeling and Simulation Vehicle Dynamics Software

Linked Companies

Claytex
$1M to $5M