During a migration validation project, a colleague (T1) uses Google Docs/Sheets for coding and refuses to adopt version control. Their unclear methods and inconsistent support have created serious workflow issues. Any suggestions?
I have dealt with a similar situation on a project where determining the best method of version control was challenging at first. My experience taught me that starting with a practical demonstration of Git’s effectiveness in managing changes can help showcase its value over tools like Google Docs. In one instance, setting up a small test repository and highlighting how issues were quickly identified and resolved helped shift the team’s perspective. The key is to contrast the benefits of traceability and collaboration against the risks of data loss and miscommunications that often accompany unstructured methods.
Having experienced similar challenges, I found that a gentle introduction to version control can often demonstrate its value. By presenting a pilot project with Git, I was able to show how tracking changes, merging reusable components, and establishing clear audit trails significantly streamlined our processes. Emphasizing the benefits of consistency and long-term reliability over immediate convenience helped shift the perspective. Using version control is not just about discipline but also about enabling smoother collaboration and reducing repeated manual work down the line.