Git Immersion
Few tools have changed the way I work as much as the git source control system. Its distributed nature and lightweight branching and merging have made it possible for me to massage my code base in ways I couldn’t have even imagined before using git.
However, git has a reputation for being hard to learn. Because of its rather different approach to source control issues, many of the techniques we have learned in other source control systems do not translate cleanly when using git.
In this workshop we take two approaches to dealing with the whole “fear of git” issue. First, we explain git from first principles by using an easy to understand, step by step model that leaves nothing to fear. Second, we actually use git in more or less real situations, and become familiar with the tool by using it.
So, whether you are a complete newcomer to git, or have been using it a while but would like a deeper understanding, this workshop is for you.
Attendees of this workshop should bring a wifi-enabled laptop with Git installed and ready to go.
Jim Weirich
EdgeCase LLC
Jim Weirich is the Chief Scientist for EdgeCase LLC, a Rails development firm located in Columbus Ohio. Jim has over twenty-five years of experience in software development. He has worked with real-time data systems for testing jet engines, networking software for information systems, and image processing software for the financial industry. Jim is active in the Ruby community and has contributed to several Ruby projects, including the Rake build system and the RubyGems package software.
Comments on this page are now closed.
Comments
I loved the first part about “csc” building up from first principles. The “quiet” lab stuff was somewhat less appealing.
lab corrections lab 11 – Rakefile should read require ‘lib/hello’ lab 15 – lib/hello.rb missing require ‘greeter’ lab 16 – at end switch to master for lab 17 lab 24 – git clone hello2 cloned_hello lab 27 – ls hello.git #NOT git ls hello.git lab 31 – git clone git://localhost/hello.git network_hello
Excellent prepared material. Jim’s discussion was first rate. I would have liked much more of that, and while I know there was supposed to be lab time, I could have used less of that and more discussion and explanation of advanced topics.
Good intro to git. Jim did a great job explaining what he covered. Thought it was gonna go “deeper” w/ more concrete/complex examples. Maybe replace some of the lab w/ practical/real-life examples from the audience?
Good, as much as there was. Just when things started to get “deep,” we had an hour and a half of empty lab time. It left me feeling like I had about half a tutorial.
Slides could have more/better explanations. Not enough time spent on the more advanced topics for the later slides/labs.