5 edited body
source | link

If they have that down, you can explain how git pull is really git fetch && git merge; how all repositories actually contain exactly the same objects (git mergefetch is almost the same as copying stuff over with scp inside the git object directory) and so on.

If they have that down, you can explain how git pull is really git fetch && git merge; how all repositories actually contain exactly the same objects (git merge is almost the same as copying stuff over with scp inside the git object directory) and so on.

If they have that down, you can explain how git pull is really git fetch && git merge; how all repositories actually contain exactly the same objects (git fetch is almost the same as copying stuff over with scp inside the git object directory) and so on.

4 Some overly verbous stuff removed
source | link

I'm afraid I have a rather bleak view on this. I have been in exactly your shoes - I'm a git nerd and wanted to transform a team away from svn with, let's face it, minuscule results. In my case it has lead to me actively changing my own perception on things like this, and accepting that some things, regarding people, just cannot be forced"forced to happiness". People are not computers, it is incredible hard to "program"program them. I am still happy for having tried, it has shown me in a rather soft way what I do and what I do not want to do in my professional life.

Also, really grokking git requires an intense interest in abstract data structures. It may sound unbelievable, but in my experience there are programmers who have no interest in things like that at all and who are bored and overburdened by thingselements more complex than simple arrays. You can argue back and forth whether those should be doing the job they are doing, but it is what it is.

I am talking about add, commit, in conjunction with the local working directory and the stage (make sure they understand that the working directory is not the same as the staging area which is not the same as the repository).

These things can take a few hours of diligent explaining with a hello world repository.

I'm afraid I have a rather bleak view on this. I have been in exactly your shoes - I'm a git nerd and wanted to transform a team away from svn with, let's face it, minuscule results. In my case it has lead to me actively changing my own perception on things like this, and accepting that some things, regarding people, just cannot be forced. People are not computers, it is incredible hard to "program" them. I am still happy for having tried, it has shown me in a rather soft way what I do and what I do not want to do in my professional life.

Also, really grokking git requires an intense interest in abstract data structures. It may sound unbelievable, but in my experience there are programmers who have no interest in things like that at all and who are bored and overburdened by things more complex than simple arrays. You can argue back and forth whether those should be doing the job they are doing, but it is what it is.

I am talking about add, commit, in conjunction with the local working directory and the stage (make sure they understand that the working directory is not the same as the staging area which is not the same as the repository).

These things can take a few hours of diligent explaining with a hello world repository.

I'm afraid I have a rather bleak view on this. I have been in exactly your shoes - I'm a git nerd and wanted to transform a team away from svn with, let's face it, minuscule results. In my case it has lead to me actively changing my own perception, and accepting that people, just cannot be "forced to happiness". People are not computers, it is incredible hard to program them. I am still happy for having tried, it has shown me in a rather soft way what I do and what I do not want to do in my professional life.

Also, really grokking git requires an intense interest in abstract data structures. It may sound unbelievable, but in my experience there are programmers who have no interest that at all and who are bored and overburdened by elements more complex than simple arrays. You can argue back and forth whether those should be doing the job they are doing, but it is what it is.

I am talking about add, commit, in conjunction with the local working directory and the stage (make sure they understand that the working directory is not the same as the staging area which is not the same as the repository).

3 added 568 characters in body
source | link

This answer tries to address how to get senior programmers interested in git, not about how to learn git the quickest way - for that, the excellent git book is great, or any amount of tutorials (=> Google). Good links to go with this answer are Git is a purely functional data structure or especially the short How git stores your data.

I'm afraid I have a rather bleak view on this. I have been in exactly your shoes - I'm a git nerd and wanted to transform a team away from svn with, let's face it, minuscule results. In my case it has lead to me actively changing my own perception on things like this, and accepting that some things, regarding people, just cannot be forced. People are not computers, it is incredible hard to "program" them. I am still happy for having tried, it has shown me in a rather soft way what I do and what I do not want to do in my professional life.

I'm afraid I have a rather bleak view on this. I have been in exactly your shoes - I'm a git nerd and wanted to transform a team away from svn with, let's face it, minuscule results. In my case it has lead to me actively changing my own perception on things like this, and accepting that some things, regarding people, just cannot be forced. People are not computers, it is incredible hard to "program" them. I am still happy for having tried, it has shown me in a rather soft way what I do and what I do not want to do in my professional life.

This answer tries to address how to get senior programmers interested in git, not about how to learn git the quickest way - for that, the excellent git book is great, or any amount of tutorials (=> Google). Good links to go with this answer are Git is a purely functional data structure or especially the short How git stores your data.

I'm afraid I have a rather bleak view on this. I have been in exactly your shoes - I'm a git nerd and wanted to transform a team away from svn with, let's face it, minuscule results. In my case it has lead to me actively changing my own perception on things like this, and accepting that some things, regarding people, just cannot be forced. People are not computers, it is incredible hard to "program" them. I am still happy for having tried, it has shown me in a rather soft way what I do and what I do not want to do in my professional life.

2 added 378 characters in body
source | link
1
source | link