> How would you describe or recommend that process to someone in a technical non-dev role that has never used source control? That’s the audience though. I kno

> How would you describe or recommend that process to someone in a technical non-dev role that has never used source control? That’s the audience though. I know technical non-devs in various roles that would kill for the kind of features that git provides. They’re stuck manually versioning files. There is definitely a market out there for something like this but even simple version control is very tricky for non-devs. It’s just something we’re more intitivively good at probably to do with how we approach breaking down problems. Animators, graphic designers, architects etc tend to think more holistically. If they use these tools at all they’re usually a service provided by some in house experts, such as the engineering team or IT.