Using git's bisect to find out where it all broke

When working on a project with with several contributors, it can be quite a pain if the lastest commit breaks. Using blame is one way to go, but if this doesn't yield the solution or the
place where shit went wrong, git bisect can be used to systematically track the point or commit
where things broke, which is a nice debugging tool.

Here's a nice tutorial on the matter: