4 ms·
Just to clarify; I am not saying that there isn't a use case. I am just questioning whether it is the general case that products should designed around and mayb
by chvid 8y ago
Just to clarify; I am not saying that there isn't a use case. I am just questioning whether it is the general case that products should designed around and maybe that is the reason why we don't see more of it.
If you have 4 people writing a book together would you really sit there in realtime with 4 cursors and typing away on the same document? Or would you structure, delegate and spread things out across time and space (doing most of the work) and then later edit and merge it together.
- vidarh 8y agoI work in a team of 15 people where our last offsite was planned mostly on a single Google Docs document where we all edited sections, marked checklists, added comments at the same time. The other day I was in our company flat that doubles as occasional office, and three people in the flat and one remote all edited the same document at the same time. This is business as usual for us. We'd still structure, delegate and spread things out across time and space, but why should we need to do it in separate documents? It adds effort to copy and merge things and shift things around. Sometimes one person writes a part and passes it off to another person (or three) to proofread and edit, and they may move paragraphs around, or copy in paragraphs from another section.
- reificator 8y ago> Or would you structure, delegate and spread things out across time and space (doing most of the work) and then later edit and merge it together. I tend to have the programmer's mindset about things like this. Put it in version control and let the VCS tool help you split and merge and fork and pull as well as track your changes over time and the reasoning behind them. You tend to favor the workflow you know, after all.