🎉 October Learning Month — learn a new software term every day!
An interactive flashcard trainer for software engineering terms.

Blame

In plain terms

Showing who last changed each line of a file.

Going deeper

git blame annotates each line with the commit and author who last modified it, helping trace when and why code changed. It attributes every line.

Under the hood

Useful for understanding history and finding context, not for assigning fault despite the name.

Examples

git blame, code archaeology, finding change context, debugging history.

Think of it like...

Like a margin note on each line saying who wrote it and when.

Feedback & Bug Report