A confused Git user. There was a recent complaint on Git User mailing list . Quote: Why do I have to be a source control engineer just to be a software developer? Now, the main issue of this poor person is that his organization has failed to on-board him into his job. They told him to use Git, but didn't give him the means to do so productively (as far as we know, anyway). What I started wondering was: Could his employer somehow have set up Git for him so that he could work with it just as easily as with Subversion? Given a prepared .gitconfig with all the aliases and configurations that you wanted, could you really dumb down Git so much that it would be analogous to the simpleness of SVN? Well, here's my take on it: To a certain degree: yes. If you could narrow down Git to do the most typical two SVN commands: update (pull without merging), and commit (with push) .. that would help a lot. Dumbing down pull The first step would be to make git pull as stup
My thoughts on software development.