TFS or Git
-
I've used TFS. While the Web UI mildly annoying, I know it and it works. Git however is a whole different animal. To me it seems very confusing and difficult to work with. What are you guys using? What's the standard these days?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
I believe the standard is more or less GIT. We switch from Subversion to GIT (hosted on ButBucket) a year ago, and we use TortoiseGit as a front end. The transition was hard; learning curve is very steep. The thing with GIT is that it has a lot of advanced features that you need to keep clear of that most people do not use. Doing simple Code Versionning is easy. (clone, checkout, pull, push commit ...) Branching is fun and more or less seamless (we do branches for each issue) once you "get it". This is one tutorial that I used. [Git Tutorials and Training | Atlassian Git Tutorial](https://www.atlassian.com/git/tutorials)
I'd rather be phishing!
-
Are there any Agile tools that work (well) with Git?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
I'm still new-ish to git myself, but there's always Jira[^] which will do that. It's like $10 if you host it yourself. As long the concepts are down I'd imagine you could find a way to adopt most tools to the workflow though. Anyway, here is the basic concept of agile within git: How Git fits into an agile workflow[^]. Since git makes branching much easier, you'll see people use them a lot more.
Jeremy Falcon
-
I've used TFS. While the Web UI mildly annoying, I know it and it works. Git however is a whole different animal. To me it seems very confusing and difficult to work with. What are you guys using? What's the standard these days?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
I've used TFS. While the Web UI mildly annoying, I know it and it works. Git however is a whole different animal. To me it seems very confusing and difficult to work with. What are you guys using? What's the standard these days?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
I use Git begrudgingly. Worst part of the learning curve is that if you have a file X.txt in branch A but not in branch B when you switch branches from A to B X.txt vanishes. It will come back when you switch back as long as it was checked in. It focuses on the repository as a whole rather than individual files. Get a good ide for Git, they help and have all the features one normally needs. I'm enjoying GitKraken right now but have used SourceTree as well.
-
I use Git begrudgingly. Worst part of the learning curve is that if you have a file X.txt in branch A but not in branch B when you switch branches from A to B X.txt vanishes. It will come back when you switch back as long as it was checked in. It focuses on the repository as a whole rather than individual files. Get a good ide for Git, they help and have all the features one normally needs. I'm enjoying GitKraken right now but have used SourceTree as well.
MarkTJohnson wrote:
It focuses on the repository as a whole rather than individual files.
I find that's part of what makes branching incredibly easy in git though. Less is more.
Jeremy Falcon
-
A_Griffin wrote:
I am just so glad I work alone….
Hah! That makes two of us! I still have a coworker that does mostly non-coding stuff. I've made it almost 20 years without source control...code fearlessly! :laugh:
"Go forth into the source" - Neal Morse
-
MarkTJohnson wrote:
It focuses on the repository as a whole rather than individual files.
I find that's part of what makes branching incredibly easy in git though. Less is more.
Jeremy Falcon
To each his own. I prefer the old days with file locking. But the files disappearing between branches was is real PITA at times when you want to compare files.
-
To each his own. I prefer the old days with file locking. But the files disappearing between branches was is real PITA at times when you want to compare files.
MarkTJohnson wrote:
To each his own. I prefer the old days with file locking.
:-D Fair enough.
MarkTJohnson wrote:
But the files disappearing between branches was is real PITA at times when you want to compare files.
Well, you can do a diff across branches. Not sure what to click in Tortoise for it, but it has to support it since git does.
Jeremy Falcon
-
I'm using versioncontrol also for private stuff.
Wrong is evil and must be defeated. - Jeff Ello
-
I've used TFS. While the Web UI mildly annoying, I know it and it works. Git however is a whole different animal. To me it seems very confusing and difficult to work with. What are you guys using? What's the standard these days?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
Git is an immense over kill. SO complex, so powerful, so much more than you need, but it works. Very very well. Take the time to get to know it, the online support is very good. You will, after a few years, wonder why you use anything else.
-
I've used TFS. While the Web UI mildly annoying, I know it and it works. Git however is a whole different animal. To me it seems very confusing and difficult to work with. What are you guys using? What's the standard these days?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
I made a pretty extensive research on the subject a few years ago and decided for Mercurial instead. If you want to change your VC system you should anyway really opt for a distributed one. Mercurial is filebased while Git is having a little database, so Git is having much better performance on large repositories (Yes, I'm oversimplifying things) This is not the reason Git became the defacto standard. Almost everything else is better with Mercurial, especially the learning curve. It was because when Linus Torvalds was choosing a DVC for Linux, he really liked a GIT function called Rebase, which allowed him to completely remove edits from people he considered idiots.
Wrong is evil and must be defeated. - Jeff Ello
-
I'm using versioncontrol also for private stuff.
Wrong is evil and must be defeated. - Jeff Ello
-
I've used TFS. While the Web UI mildly annoying, I know it and it works. Git however is a whole different animal. To me it seems very confusing and difficult to work with. What are you guys using? What's the standard these days?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
Wrong is evil and must be defeated. - Jeff Ello
-
I've used TFS. While the Web UI mildly annoying, I know it and it works. Git however is a whole different animal. To me it seems very confusing and difficult to work with. What are you guys using? What's the standard these days?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
Use GIT It is ugly and non intuitive which makes you think very carefully about what you are doing with it and be frugal. Use C++ for the same reason. :-)
-
Well, I do too - but as a single developer I can use my own (very) simplified methods, which double as a backup system.
I use Mercurial, it's nonintrusive, filebased (i.e. easy to backup) and easy to use. And powerful when you need it.
Wrong is evil and must be defeated. - Jeff Ello
-
TFS and Git are not mutually exclusive? :confused: Do you mean TFVC, the Microsoft Team Foundation Version Control that not even Microsoft is using anymore? TFS supports both TFVC and Git, but I'd recommend Git. In fact, TFVC shouldn't even be an options anymore because, as said, not even its creator Microsoft uses it anymore. Branching and merging is a lot better and easier in Git. Besides, Git has become the industry standard making it easier to find help and documentation. I've also heard good things about Mercurial by the way. And I guess SVN is still an options too, although I never hear about it anymore. I'm not sure if those are supported in TFS though :)
Best, Sander Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
Since I've been using both Git and TFS I can only recommend Mercurial.
Wrong is evil and must be defeated. - Jeff Ello
-
I really only care about Source Control. Do you have any "getting started" resources?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
Kevin Marois wrote:
"getting started" resources?
I think there is a lot of tutorials on youtube, actually. I find those to be the best versus just reading text about something.
-
Wrong is evil and must be defeated. - Jeff Ello
:rolleyes:
Jeremy Falcon
-
I made a pretty extensive research on the subject a few years ago and decided for Mercurial instead. If you want to change your VC system you should anyway really opt for a distributed one. Mercurial is filebased while Git is having a little database, so Git is having much better performance on large repositories (Yes, I'm oversimplifying things) This is not the reason Git became the defacto standard. Almost everything else is better with Mercurial, especially the learning curve. It was because when Linus Torvalds was choosing a DVC for Linux, he really liked a GIT function called Rebase, which allowed him to completely remove edits from people he considered idiots.
Wrong is evil and must be defeated. - Jeff Ello
I also prefer Mercurial, but everyone seems to use git, so I switched so I can more easily collaborate. And I now use GitHub, so more reason for git. Linux Torvalds likes git because he created it! Bazaar (another distributed source control system), git and Mercurial were all released within a month of each other back in 2005.
-
I really only care about Source Control. Do you have any "getting started" resources?
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
If source control is the only thing you care about, TFS should be more than adequate.
