This past week I got a new book published. It has nothing to do with programming (although in a way it has everything to do with it). Working with artists and game designers over the past I noticed how difficult it was for them to learn how to use a source control tool, and how much their work suffered by it. They had to constantly depend on someone else, usually a programmer, to commit their changes to a project’s repo, and were completely cut out from the rest of the team as far as the workflow went.
Even through there were many GUI tools available, for Git and Mercurial, there were not that many easy to follow tutorials out there.
I use Git for everything I do. Absolutely everything: code, art, writing… I can’t imagine myself working without it. It’s like having super powers; you can control time. When something goes wrong and large sections of a project need to be reworked… there’s simply no better tool to help you out through the process.
So this book is about that, it’s about Git and about SourceTree, and how all your digital work can benefit from using source control.
So this book is a careful, step-by-step guide to all that, for coders and non-coders.
If you know an artist out there who needs this thing, let him or her know.
The book is called Learning Source Control with Git and SourceTree