Key Git Concepts Explained the Hard Way

Re:Key Git Concepts Explained the Hard Way by GiorgioG on Wednesday March 14, 2018 @05:03PM (#16588276)

Similar experience here - I had a team of developers who had to move off of an internal TFS server to Bitbucket / git. I gave them all of the reference/doc links, gave them a brief overview about how git in fundamentally different than a centralized VCS. At the end of several sessions w/git (using git bash on Windows), their comment to me was: "But we're using to clicking on buttons in Visual Studio"

[ Parent | on HN ]

Re:Key Git Concepts Explained the Hard Way by userbinator on Wednesday March 14, 2018 @11:13PM (#16590182)

Visual Studio has a GUI for git, if your developers feel more comfortable that way, but in my limited experience I've had to help a few others who accidentally committed more files than they intended to using it, so the opaqueness of the GUI may be a disadvantage here.

[ Parent | on HN ]

Re:Key Git Concepts Explained the Hard Way by skocznymroczny on Thursday March 15, 2018 @08:37AM (#16592267)

Does it also support Github pull requests and Gerrit reviews? From what I've seen, people rarely use "just" git.

[ Parent | on HN ]

Re:Key Git Concepts Explained the Hard Way by flukus on Wednesday March 14, 2018 @08:23PM (#16589566)

The problem is even deeper than that, with a lot of IDE developers and particularly Visual Studio ones there entire world is in the IDE, anything outside of it may as well not exist, anything the IDE can't do is impossible. Many wouldn't even be able to compile there own projects if you took the IDE away.

An email I got the other day was "we can't debug problem with x because it's built on the CI server" and the problem was in the first few milliseconds of startup so "attach to process" was no good, even if they knew that was possible. The idea of using a debugger outside of the IDE (mdbg in this case) never crossed their mind.

IDE's a great for coding, but too many devs are way to reliant on them.

[ Parent | on HN ]

Re:Key Git Concepts Explained the Hard Way by seanmcdirmid on Thursday March 15, 2018 @07:23AM (#16591828)

Why shouldn’t they be? Why should compiling a file or debugging a project require so much command line hackery? Why can’t IDEs actually do what they promised (integrate dev tools and make them more usable)?

It is so weird that in the 90s I could do MORE in my IDE than I can today, somehow our tools have trended to increasing complexity while IDE advancement has come almost to a stand still, with a preference to simpler less integrated ones (e.g. VS Code).

[ Parent | on HN ]

Re:Key Git Concepts Explained the Hard Way by dotancohen on Sunday March 18, 2018 @07:38AM (#16611472)

I used to feel the same way, especially as a VIM user. Why is every IDE worse than VIM, and why do I have to learn a new IDE for Python, C++, PHP, and Java?

Enter the Jetbrains IDE. The same basic program for almost every programming language and a terrific VIM plugin to boot. It's on the order of $100 per year. Well worth the cost, and the only non-FOSS code on my computer other than the MP3 codecs.

I usually don't use the built-in Git commands in PyCharm, but I do use the built-in terminal to perform Git operations. The only Git work I do with the IDE directly is resolve merge conflicts, because that specific tool is terrific.

[ Parent | on HN ]