> I actually think this hyper-granular realtime collaboration like in Google docs is slightly overrated.
I have to disagree. It's absolutely necessary for a lot of workflows, especially when people are collaborating on a doc in real time during a meeting (super super common), or when you've got 10 reviewers of a doc all leaving their feedback in comments, and comments responding to comments, over the course of the same hour.
The model of clean commits works well for code. It doesn't work well at all for business team documents that are in-progress.
Heh I’m glad that there’s disagreement. I think I was even surprised myself coming to this conclusion.
> It's absolutely necessary for a lot of workflows, especially when people are collaborating on a doc in real time during a meeting
Well yeah you included the solution in the problem description. I’m not convinced of either the shared control, the talking-typing multitasking or even that the artifact should be a document. Assuming the meeting shouldn’t have been an email in the first place.
> when you've got 10 reviewers of a doc all leaving their feedback in comments over the course of the same hour
This one is easier for me to argue concretely. Shared control with 10 people is awful imo. Suggestions with click to accept can make it better (but then you have a notification problem). But what I really dislike is this perpetual state of work in progress. I think a cyclic workflow is better, with drafts and publish and much less back and forth.
In summary, I’d say that the promise of async work (which is good) ended up being sync instead - for the purposes of the human brain. I don’t want to context switch because Bryan fixed a spelling mistake, or see Janice typing out another bullet point right under mine.
I have to disagree. It's absolutely necessary for a lot of workflows, especially when people are collaborating on a doc in real time during a meeting (super super common), or when you've got 10 reviewers of a doc all leaving their feedback in comments, and comments responding to comments, over the course of the same hour.
The model of clean commits works well for code. It doesn't work well at all for business team documents that are in-progress.