Final_FINAL_v7.docx is not a version control strategy
EVENT: Join The Register for dinner in London on 24 November and hear, off the record, how your peers are fixing it.
On Tuesday, November 24, The Register and LucidLink hosted a dinner for senior technology, infrastructure, and data leaders at the Covent Garden Hotel. Joe Fay of The Register chaired the event, which focused on the issue of multiple file versions across organizations. The problem is evident in folders containing files like "final," "final2," and the actual file currently in use, often shared via email with contractors.
As different teams attempt to manage these various copies, arguments arise when two people simultaneously edit distinct versions. Each unique approach also adds storage space, burdening IT with the challenge of maintaining visibility across all locations. To counteract this, some teams independently developed their own sync services due to dissatisfaction with the approved solution's performance.
During the dinner, attendees shared real-life experiences, including a team that built a sync service and a leaver who could still access files months after leaving the organization. The conversation expanded to cover unstructured data growth, duplicate storage accumulation, and security risks associated with dispersed access. The attendees also discussed modernization strategies without discarding existing storage and governance investments.
Dinner commenced at 6:30 pm, followed by an extended discussion around one table until 9 pm. Places for the event were limited and granted under invitation, with each confirmation made personally. The dinner was sponsored by LucidLink.
Written by urgent.news from The Register Science's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
Also reported by 1 other outlet
- Final_FINAL_v7.docx is not a version control strategy theregister.com