Geek asks and answers

How can I explain source control (Mercurial / Tortoise specifically) to a non-programmer?

Our company uses Mercurial to version control a Java web application. It worked so well that we started using a control source for heaps of content (PDF files). This worked amazingly for our deployment model, and fortunately, our graphic designer was a web developer at that time and already understood the initial control.

Now we have replaced this guy with two strictly for graphic print designers. They are amazing in what they do, but they look scared and confused every time we ask them to use source control. For reference, we use Tortoise, as we have found that this was the best option for non-programmers because of its user interface.

Hginit.com is a great way for programmers to learn Mercurial, now what about a website for non-programmers?

Any ideas?

+5
source share
4 answers

I would explain to them that he would like to make a photocopy of your art project. During drawing, you can discard what you have done and continue from the previous point in time. You can also see what happens if you start in the other direction with one of your paintings. You can also give a copy to a friend and tell them that they can finish drawing trees and sky in the background. Later, you can combine both your efforts and see how it looks. Your friend can also take intermittent shots while they work in the sky and trees. Think about the possibilities!

+4

"" "" . , "", , " " " , ".

+1

, , , . , ...

trunk ; - branch , tag .

, check-in , update - checkout - .

, , , .

0

, Git . , :

  • , - " ".
  • , "", / .
  • , "" (, , ) , , " " .
  • ! (.. , , .. / )
  • .

:

, -, , , :

  • DAW (Logic Pro, et al.)
  • Somewhat accepts
  • Several remixes, producing or mastering take place

Sometimes I create and test a new experimental branch to try a completely different approach to composition composition and / or production. Usually this affects several elements from the above list, but I can confidently move forward, knowing that if something does not work completely correctly, I can always switch to a “stable” version of the project.

Version control is not just for the "source". This is great for any creative digital project of significant scale!

0
source

More articles:


All Articles