4 ms·
A couple things... First, git doesn't especially solve problems that CS majors have until they are near the end of their courses. The need to manage collaborat
by jmull 2y ago
A couple things...
First, git doesn't especially solve problems that CS majors have until they are near the end of their courses. The need to manage collaboration, organization, and change in a code base is trivial until pretty late in a CS program, and typically never gets past basic.
Second, the context here is the git command-line interface. People can and do use git extensively without it.
Third, git's not exactly perfect. Personally, I'll be a little sad if git remains the de facto standard source control in the long term... it's not bad, but we can do better.
I think lack of knowledge of git commands in a CS grad would be essentially uncorrelated with future professional success.
- seadan83 2y agoGit would have been helpful to me in my very first intro to programming course. It fixes those situations of: "arg, I changed one thing - it no longer works, and I'm not even sure anymore what that one thing was!" Second, a successful CS grad has hopefully written at least something that is at least 2000 lines long. Doing that without VCS of any kind is not impressive, it is obtuse. That is a strong no hire signal imo.
- WalterSear 2y agoIt's impressive all right; just the wrong kind of impressive.
- orwin 2y agoI had a different CS course than you, because git (as a remote storage and version control tool, using branches and submodules came later) and bash were the two first thing I had to learn on the first day (how to use diff and patch was on the second day if I remember right).
- noway421 2y ago> git's not exactly perfect Somewhere in an alternative universe, we're building all of our version control tooling on top of Pijul... Maybe even with AST-aware diffing.