Agreed. Stack Overflow would occasionally get questions (though it's less common these days) along the lines of, "I worked 5 years at my last job developing code managed in Subversion, but at my new job they use git..." or "We want to move our codebase from [some commercial centralized VC] to Github"..." always ending with "What are the differences between the thing I know and git, and what are the equivalent git commands for the steps/functions/operations I know how to perform in the old system?"
If the person asking that question is unlucky, someone would do them a disservice and answer it as asked. When the only right answer, really, is to explain that git is fundamentally a completely different paradigm from systems like CVS, svn, and the like. The worst way someone can approach git is from the mindset of learning how to apply their centralized-VC patterns with git. They'll be constantly surprised by the results of their actions, constantly confused why things are so much harder and more complicated than they should be, and never even glimpse the true power and beauty of how git is MEANT to work.
New paradigms require new understanding, throwing away everything we think we know and re-learning from the ground up. That's the only way to approach git if you're going to have any hope of eventually understanding it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Agreed. Stack Overflow would occasionally get questions (though it's less common these days) along the lines of, "I worked 5 years at my last job developing code managed in Subversion, but at my new job they use git..." or "We want to move our codebase from [some commercial centralized VC] to Github"..." always ending with "What are the differences between the thing I know and git, and what are the equivalent git commands for the steps/functions/operations I know how to perform in the old system?"
If the person asking that question is unlucky, someone would do them a disservice and answer it as asked. When the only right answer, really, is to explain that git is fundamentally a completely different paradigm from systems like CVS, svn, and the like. The worst way someone can approach git is from the mindset of learning how to apply their centralized-VC patterns with git. They'll be constantly surprised by the results of their actions, constantly confused why things are so much harder and more complicated than they should be, and never even glimpse the true power and beauty of how git is MEANT to work.
New paradigms require new understanding, throwing away everything we think we know and re-learning from the ground up. That's the only way to approach git if you're going to have any hope of eventually understanding it.