Right. Maybe a shared time machine archive can solve the issue.
Mattia Astorino
1

In my opinion, to be able to have branches and merging them is as important as having access to a file’s history, especially for team work. It makes the assets much more manageable. In some projects, my team ended up doing a lot of copy-pasting across files from 1 project (everyone had their own), which is incredibly inefficient to synch files. Not only that, but to me it’s about making a more workflow that evolves seamlessly between designing and implementing, where both tech & design are working with a similar process or tools especially when it comes to production.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.