3 ms·

> It's yet another 'let's recreate git from scratch, kinda' post. I don't think that's what it's doing. It's just trying to explain what git does through analo

> It's yet another 'let's recreate git from scratch, kinda' post. I don't think that's what it's doing. It's just trying to explain what git does through analogy and example. A remarkable number of people never grok that git is basically just a version control repository for source code (checkout/commit) that itself has been checked into a version control repository for VC repositories (pull/push). There's lots of reasons for it doing that, most of which are grounded in the fact that lots of developers only learn just enough VC to satisfy their immediate coworkers, and otherwise treat it like a magic black box. Did you ever notice that after git became popular that colleges started to teach CS students to use version control? Ever think about why that might be?

compiler-guy 5y ago
Schools were teaching version control long before git.
ryanianian 5y ago
> Did you ever notice that after git became popular that colleges started to teach CS students to use version control? Ever think about why that might be? Because schools have recognized the need to teach some pragmatic tools in addition to pure theory? I had a "tools" class in undergrad 15 years ago. Learned shell, perl, pcre regexes, make, cvs, subversion, etc. They created the class due to the perception of new-grads being unable to use real-world tools to do real work. Since then, many schools have adopted a similar approach: either a dedicated class or treating many classes as "project"-style classes that use real-world toolsets and SDLCs.
detaro 5y ago
> Did you ever notice that after git became popular that colleges started to teach CS students to use version control? Not really, no. Theory-focussed ones still might not. Practical ones did already teach Subversion etc. Some teach git by teaching the full logic behind it, others as "here's some basic commands you need, everything else is on you if you want to learn it, you won't need it to pass".

compiler-guy 5y ago

Schools were teaching version control long before git.

ryanianian 5y ago

> Did you ever notice that after git became popular that colleges started to teach CS students to use version control? Ever think about why that might be? Because schools have recognized the need to teach some pragmatic tools in addition to pure theory? I had a "tools" class in undergrad 15 years ago. Learned shell, perl, pcre regexes, make, cvs, subversion, etc. They created the class due to the perception of new-grads being unable to use real-world tools to do real work. Since then, many schools have adopted a similar approach: either a dedicated class or treating many classes as "project"-style classes that use real-world toolsets and SDLCs.

detaro 5y ago

> Did you ever notice that after git became popular that colleges started to teach CS students to use version control? Not really, no. Theory-focussed ones still might not. Practical ones did already teach Subversion etc. Some teach git by teaching the full logic behind it, others as "here's some basic commands you need, everything else is on you if you want to learn it, you won't need it to pass".