Jump to content

  • Log In with Google      Sign In   
  • Create Account

We're offering banner ads on our site from just $5!

1. Details HERE. 2. GDNet+ Subscriptions HERE. 3. Ad upload HERE.


Don't forget to read Tuesday's email newsletter for your chance to win a free copy of Construct 2!


#ActualStinkfist

Posted 21 January 2013 - 05:39 PM

Simply learn both SVN and Git. I'd highly recommend learning SVN first, due to Git's steep learning curve. SVN will give you a decent understanding of VCSs in general quickly, after which you can hop into more advanced topics. I personally first hated Git when I tried to learn (and am still learning...) it after SVN, but once I got some sort of hold of it, I realized there's no going back (to SVN). As your focus is in making games, you probably end up using SVN more, assuming you will work with not-so-tech-savvy people (artists etc.). If you can, use TortoiseSVN and TortoiseGit - they'll make your life a lot easier.

#8Stinkfist

Posted 21 January 2013 - 05:38 PM

Simply learn both SVN and Git. I'd highly recommend learning SVN first, due to Git's steep learning curve. SVN will give you a decent understanding of VCSs in general quickly, after which you can hop into more advanced topics. I personally first hated Git when I tried to learn (and am still learning...) it after SVN, but once I got some sort of hold of it, I realized there's no going back (to SVN). As your focus is in making games, you probably end up using SVN more, assuming you will work with also not-so-tech-savvy people (artists etc.). If you can, use TortoiseSVN and TortoiseGit - they'll make your life a lot easier.

#7Stinkfist

Posted 21 January 2013 - 05:37 PM

Simply learn both SVN and Git. I'd highly recommend learning SVN first, due to Git's steep learning curve. SVN will give you decent understanding of VCSs in general quickly , after which you can hop into more advanced topics. I personally first hated Git when I tried to learn it after SVN, but once I got some sort of hold of it, I realized there's no going back (to SVN). As your focus is in making games, you probably end up using SVN more, assuming you will work with also not-so-tech-savvy people (artists etc.). If you can, use TortoiseSVN and TortoiseGit - they'll make your life a lot easier.

#6Stinkfist

Posted 21 January 2013 - 05:37 PM

<p>Simply learn both SVN and Git. I'd highly recommend learning SVN first, due to Git's steep learning curve. SVN will give you decent understanding of VCSs in general quickly , after which you can hop into more advanced topics. I personally first hated Git when I tried to learn it after SVN, but once I got some sort of hold of it, I realized there's no going back (to SVN). As your focus is in making games, you probably end up using SVN more, assuming you will work with also not-so-tech-savvy people (artists etc.). If you can, use TortoiseSVN and TortoiseGit - they'll make your life a lot easier.</p>

#5Stinkfist

Posted 21 January 2013 - 05:35 PM

Simply learn both SVN and Git. I'd highly recommend learning SVN first, due to Git's steep learning curve. SVN will give you decent understanding of VCSs in general quickly , after which you can hop into more advanced topics. I personally first hated Git when I tried to learn it after SVN, but once I got some sort of hold of it, I realized there's no going back (to SVN). However, in real-life game projects and alike, you probably end up using a lot of SVN too as you need work with not-so-tech-savvy people (artists etc.). If you can, use TortoiseSVN and TortoiseGit - they'll make your life a lot easier.

#4Stinkfist

Posted 21 January 2013 - 05:33 PM

Simply learn both SVN and Git. I'd highly recommend learning SVN first, due to Git's steep learning curve. SVN will give you decent understanding of VCSs in general quickly , after which you can hop into more advanced topics. I personally first hated Git when I tried to learn it after SVN, but once I got some sort of hold of it, I realized there's no going back (to SVN). However, in real-life game projects and alike, you probably end up using a lot of SVN too as you need work with not-so-tech-savvy people (artists etc.).

PARTNERS