3 ms·
The same scenario that software engineers use it for: Combining work from multiple collaborators into a coherent whole. I don't see why this would be less usefu
by p-e-w 4y ago
The same scenario that software engineers use it for: Combining work from multiple collaborators into a coherent whole. I don't see why this would be less useful for e.g. a policy institute collaboratively writing a report than it is for programmers collaboratively developing an application.
- unlaxedneurotic 4y agoHow often would this kind of report writing, which may involve many reporters, happen in an org like that? I don't think someone would like to invest in training and tooling for something that might happen once a year.
- p-e-w 4y agoAll the time? Such institutes push out 300+ page reports on a regular basis. Do you think those are written by a single person?
- 7steps2much 4y agoWhile that is true, one could argue that these reports are either split into distinct parts written by individual authors or are not written in parallel. A report doesn't have ten people writing the same page. If everyone writes a chapter then merging is trivial. No need to learn a complex tool
- vertere 4y agoFor drafting yes, but at some point someone will probably want to edit or review the parts collectively. It's easy to prematurely consolidate the chapters into one file, and then any further changes have to be merged into the 'master'. A proper VCS can help here.