7 ms·

Don't you think there is a sensible reason why writers don't merge branches?

• icebraining 12y ago
  What makes you think they don't? They just do it manually. https://en.wikipedia.org/wiki/Collaborative_writing https://en.wikipedia.org/wiki/Collaborative_writing https://en.wikipedia.org/wiki/Collaborative_fiction https://en.wikipedia.org/wiki/Collaborative_fiction
  • learnstats2 12y ago
    In fact, I've been involved in collaborative writing and it was organised so that it didn't require any awkward merging procedure. 'Git skills' take people away from writing. Or, put another way, 'git skills' increase cognitive load on programmers and is just another area where mistakes can be made.
    • icebraining 12y ago
      In fact, I've been involved in collaborative writing and it was organised so that it didn't require any such thing. That just means your group chose to limit the potential quality of the work (by not allowing people to improve on other's parts) or expand the timespan of the project (by disallowing concurrent editing) on behalf of simplifying the process. They're valid tradeoffs, but too limiting for most software projects, in my opinion.
      • learnstats2 12y ago
        I would argue the exact opposite, but I don't think we are getting anywhere :)
• detaro 12y ago
  They do, but it is a feature in Word and therefore not part of the Dropbox game ;)