Git is simply too hard
-
I totally agree with this. Having spent many years using other version control systems, I've found Git the hardest to get to grips with. Conceptually it's quite simple, but at the detailed level it's insidiously difficult.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
-
I totally agree with this. Having spent many years using other version control systems, I've found Git the hardest to get to grips with. Conceptually it's quite simple, but at the detailed level it's insidiously difficult.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
Agreed, and when stuff goes even slightly wrong, it gets difficult rapidly. SVN was transparent most of the time (especially with TortoiseSVN. Even SourceSafe was easier (until you got to the point where it would break - just before launch usually)
TTFN - Kent
-
Agreed, and when stuff goes even slightly wrong, it gets difficult rapidly. SVN was transparent most of the time (especially with TortoiseSVN. Even SourceSafe was easier (until you got to the point where it would break - just before launch usually)
TTFN - Kent
Gimme good old PVCS, Lock those files down until I'm done with them.
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated.
-
Gimme good old PVCS, Lock those files down until I'm done with them.
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated.
As long as you weren’t the guy that locked files, then went camping for a month... :mad:
TTFN - Kent
-
-
It's a lot simpler if you don't use the command line. But for some reason using a UI to hide all the absurd and complicated switches and options is like walking into a biker bar and ordering a Shirley Temple. You get beaten up for no good reason.
Latest Articles:
Thread Safe Quantized Temporal Frame Ring Buffer -
It's a lot simpler if you don't use the command line. But for some reason using a UI to hide all the absurd and complicated switches and options is like walking into a biker bar and ordering a Shirley Temple. You get beaten up for no good reason.
Latest Articles:
Thread Safe Quantized Temporal Frame Ring BufferExactly, yeah. The burly CLI folk dominate in a lot of the discussions. Most of our team has standardized on GitHub Desktop, and it's great - as long as nothing goes wrong.
TTFN - Kent
-
Exactly, yeah. The burly CLI folk dominate in a lot of the discussions. Most of our team has standardized on GitHub Desktop, and it's great - as long as nothing goes wrong.
TTFN - Kent
Kent Sharkey wrote:
Most of our team has standardized on GitHub Desktop,
I use SmartGit but my activities are really only create branches, commit, merge, resolve conflicts, and sometimes revert, which sucks (not SmartGit's fault) because you can't just merge the branch back in. Git thinks the changes have already been applied because it's in the commit change. I haven't dared to figure out how cherry picking works. One of my coworkers wants me to start doing pull requests. Given the repo is managed by BitBucket, which sucks, pull requests add a few precious minutes to the work day for each commit. And the only person qualified to review the changes is, well, basically me. So I fail to see the point, as I'd simply be approving my own pull requests! A very off-color NSFW analogy just popped into my head. :laugh:
Latest Articles:
Thread Safe Quantized Temporal Frame Ring Buffer