I graduated in 1990 in Electrical Engineering and since then I have been in university, doing research in the field of DSP. To me programming is more a tool than a job.
Glitch allows you to code collaboratively in realtime, much like Google Docs.
Urgh! 😄 Honestly, I never liked that kind of collaboration: N hands messing with the same object at the same time. I used few times with Google Docs (because others decided it was a nice option), but I never liked it.
For shared document editing I, honestly, prefer the old fashioned solution: one single editor has write privileges on the document and asks for inputs to the others. If you use the shared approach then you need a deep rewriting phase afterward since you need to clean all the "jumps" between parts written by different people. Integrating inputs received from others is much faster and easier.
If the document is very large (e.g. a book with chapter), assign a "block" (e.g. a chapter) to its own editor.
I write about learning to code, indie hacking, writing & tech for good. ✍️golifelog.com 🔌plugins.carrd.co 📋listskit.com ⛓sheet2bio.com 🏛outsprint.io 🇸🇬safedistancing.sg 💨psi.sg
I think you misunderstood. I made reference to Google Docs as an analogy to Glitch, not direct comparison. Glitch is actually for code editing, not writing a book.
Urgh! 😄 Honestly, I never liked that kind of collaboration: N hands messing with the same object at the same time. I used few times with Google Docs (because others decided it was a nice option), but I never liked it.
For shared document editing I, honestly, prefer the old fashioned solution: one single editor has write privileges on the document and asks for inputs to the others. If you use the shared approach then you need a deep rewriting phase afterward since you need to clean all the "jumps" between parts written by different people. Integrating inputs received from others is much faster and easier.
If the document is very large (e.g. a book with chapter), assign a "block" (e.g. a chapter) to its own editor.
I think you misunderstood. I made reference to Google Docs as an analogy to Glitch, not direct comparison. Glitch is actually for code editing, not writing a book.
Interesting, so you prefer "asynchronous" editing.
Makes sense.