![]() Some like to use the command line - and that's great. Mercurial (hg), Team Foundation Version Control (TFVC) and Subversion (SVN) are all examples of SCMs but Git has really taken over in the software world and is the industry standard - I'd recommend it for that on its own: there's no point teaching your team a SCM system which is (or may become) redundant.Īs for git clients, there are so many out there. SCM is not the same as a backup and if you've emailed some code to a colleague, you're probably doing it wrong!įor all the reasons I gave previously, SCM is essential for modern day software development. This isn't one of the 5, but there are seriously some organisations out there not using SCM yet. Why did the developer not want to use git? Today we'll take a look at 5 simple tips which will, with any luck, improve your git practice. People use git as a dumping ground for code rather than an well-managed archive of software. I've worked with a fair few organisations and development teams over the years, and poor git utilisation is a more common issue than you might think. I can, though, be a bit of a git about it: I'm really fussy about how people use git - and that's a good thing. Used properly, however, it can be so much more - helping ease complex processes such as release management, feature development and multiple people working concurrently. ![]() It can ensure your code is backed up, versioned and accessible to other developers. Let's start really simple: what is git? Git is the most popular Source Control Management (SCM) system. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |