Skip to content
DevMeme
3532 of 7590
VersionControl Post #3868 · source on Telegram

When git blame reveals you wrote the terrible code last year

Description

Two-panel cartoon meme set in a classroom. In the top panel, a pink-shirted student on the left, labelled with the text “git,” passes a sheet of paper to a green-shirted student on the right who is exclaiming, “This code sucks, who wrote it!!”. In the bottom panel the same green-shirted student, now frowning angrily, unfolds the paper which reads, “Commited by you year ago” (spelling error included). A small “KAPWING” watermark sits in the lower-right corner. The joke riffs on the moment a developer uses git blame to investigate bad code, only to discover the commit history incriminates their past self - highlighting common realities of code quality decline, technical debt, and self-inflicted bugs

Comments

10
Anonymous ★ Top Pick git blame: because nothing humbles a principal engineer faster than finding out Past-You thought a 500-line switch statement qualified as a plugin architecture
  1. Anonymous ★ Top Pick

    git blame: because nothing humbles a principal engineer faster than finding out Past-You thought a 500-line switch statement qualified as a plugin architecture

  2. Anonymous

    The only thing worse than inheriting a legacy codebase is realizing you're the founding architect who wrote those 'temporary workarounds' that became load-bearing infrastructure three acquisitions ago

  3. Anonymous

    The most humbling moment in any senior engineer's career: running `git blame` on that horrific code you've been complaining about in standup, only to see your own commit from 18 months ago - back when you thought nested ternaries and single-letter variables were 'elegant.' At least you can't throw yourself under the bus in the PR review

  4. Anonymous

    Git commit: 'Quick fix'. Git blame one year later: 'WTF were you thinking?'

  5. Anonymous

    Git blame: confirming 'who wrote this?' - me, during a Sev-1, five minutes before change freeze

  6. Anonymous

    At scale, git blame is just a mirror: every Sev-2 traces back to your “temporary” hotfix that survived twelve releases

  7. @Ox1DEA 4y

    A good sign if you understand it now. But if no...

  8. Aleksander 4y

    Committed by you one month ago.

  9. @nb30ac 4y

    Comitted by you one week ago (after holidays)

  10. @InputUsernameHere 4y

    It just means you improved your skills

Use J and K for navigation