How do you explain source control to a non-programmer? Our creative department head was chatting with me yesterday and said that he has no idea why we use CVS. It makes no sense to him. Despite the fact that he's been using CVS for months now, it wasn't until today that I faced the mess that his confusion has caused (and that's certainly curious timing).
I needed to update a few query strings in some HTML docs, only to find that he's been editing files directly on a server without bothering to check changes into CVS. He'll toss new files out there just to "test things out" and we don't know what goes with what. A simple change that should only have taken a few minutes is now a few hours of wading through this mess. The creative department head and I get along very well, so if I can find a way to explain it to him that he understands, he'll be receptive, but so far he's found no value in tracking older versions of what he does. Sigh.
Benefits that he should understand:
Update: Our CTO had a chat with him this morning. Apparently, as a result of that chat, the creative director went through and got everything straightened out in CVS. He wiped out all of my work from yesterday, too.