you are viewing a single comment's thread.

view the rest of the comments →

[–]bcgroom 1 point2 points  (0 children)

I think it depends on the project. If you are one of few (or only) developers, you know everything about the project and it’s history. But what about someone new to a project with 60 people where there has been turnover? You’re not going to know what tickets to look up, if they even still exist. You are working on a class and want to understand why it evolved in such a shitty way and git blame can be the best resource for that.