---
title: "Discussion on \"git blame Is Pointing at the Wrong Commit\" | Hashnode"
description: "Discussion on \"git blame Is Pointing at the Wrong Commit\". How to find out why legacy code exists before you delete it"
url: "https://hashnode.com/posts/understand-legacy-code-git-history/6abf1628c2de7a3c2d7471f1"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [git blame Is Pointing at the Wrong Commit](https://simplyexplained.hashnode.dev/understand-legacy-code-git-history?utm_source=hashnode&utm_medium=feed)

How to find out why legacy code exists before you delete it

Oct 2 · 9 min read · simplyexplained.hashnode.dev  
Read the article

-   [#software-engineering](https://hashnode.com/tag/software-engineering)
-   [#git](https://hashnode.com/tag/git)
-   [#gitlab](https://hashnode.com/tag/gitlab)
-   [#github](https://hashnode.com/tag/github)
-   [#legacy-code](https://hashnode.com/tag/legacy-code)
-   [#programming-blogs](https://hashnode.com/tag/programming-blogs)
-   [#programming-concepts](https://hashnode.com/tag/programming-concepts)
-   [#programming-languages](https://hashnode.com/tag/programming-languages)
-   [#career-advice](https://hashnode.com/tag/career-advice)

## Written by

[Adam Jaber](https://hashnode.com/@adamjaber)

@adamjaber · Delhi, India

  
[View profile](https://hashnode.com/@adamjaber)

Senior engineer. How AI and software work — and where they quietly break.

I'm a senior software engineer. I write Simply Explained, a plain-English breakdown of how AI and software actually work, and the quiet ways they break: AI fixes that hide bugs, agents that pick the wrong tool, health checks that take down healthy servers. One symptom, one analogy, one fix per piece. New here? Start with the pinned Start Here guide, or get one breakdown a week by email.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
