1. Being a Coder Made Easy
With Git, these situations do not occur so often. Big commits are made in branches where they do not disturb the workflow of others. Branches do have to get merged back at some point, and conflicts dealt with, but this happens in a planned and orderly fashion. There is no race to merge branch first.
2. Simply Explained - SVN Guinea Pig
Oh, so typical. Do not update the code when it's broken centrally. This problem is magnified in the lack of a continuous integration system or a fast build.
With Git, your active work is on a branch where you can pull in needed changes as you need them. You can also set up staging branches that run tests or code-review on incoming code, before they are merged into the main line, like they do with Gerrit.
3. Good Coders
4. Real Coders Help Eachother
5. One Day In The Life Of A Coder - Part 2
With Git, you can immediately reset to the code you had before merging in the latest changes. This takes a matter of seconds, even in a huge repository.
6. One Day In The Life Of A Coder - Part 3
With Git, you don't let these moments break your flow. You commit, use "Yada yada" as the commit message, then return later with rebase --interactive to squash, and rewrite your commits.
Dear SVN-users. It should be a wake-up call that there are actually comics making fun of one of the most fundamental and important tool in your infrastructure. Start making some changes.