|
|
|
|
|
by azov
4843 days ago
|
|
Joel's very own article on the Law of Leaky Abstractions (http://www.joelonsoftware.com/articles/LeakyAbstractions.htm...) comes to mind. Kiln Harmony might abstract away which VCS system you use, but I think in the real world you will just end up having to know both systems (or finally standardizing on one). Think of communication, for example: - How do I do blah?
- Well, you type hg blah-blah
- What's hg? - I fixed this bug on master
- Where?
- Oh, are you using mercurial? It's called a tip in your world IMHO this stuff alone makes using two almost identical but different version control systems within a team a bad idea. Then there's that another layer that is supposed to work transparently, but when you have a problem you're never quite sure... is there a bug in hg? git? kiln?.. Really, just pick one system and use it. (hint - pick git :) |
|
The only things I need to know are how to check out code, check in code, label and branch. Occasionally I create a repository. Rarely.
If you gave me a GUI that just had those four functions, I wouldn't give a rat's ass what VCS was living under the hood.