Gamers spam saves, developers push giant vague Git commits - priorities reversed
Description
Screenshot of a tweet on a white Twitter interface. The profile area shows a small circular photo of an animal, the display name “amy nguyen”, and the handle “@amyngyn”. The tweet text reads: “me playing video games: save every five minutes me writing code: git commit -am "some changes" (+647, -1049)”. Beneath the text is the timestamp “7:27 PM · 28 Sep 19 · Twitter for iPhone”. Visually, it is standard Twitter formatting with black text on a white background and blue hyperlink styling. Technically, the joke contrasts obsessive save-scumming in games with a careless single Git commit that bundles a huge diff (+647, -1049) under the meaningless message “some changes”, highlighting poor version-control hygiene and developer productivity habits familiar to seasoned engineers
Comments
6Comment deleted
The dev who quick-saves Witcher before looting a potato is also the one who labels a 1,700-line diff “some changes” - as if git rebase comes with an F5 key
The real irony is that in games you're afraid of losing 10 minutes of progress, but in coding you're willing to risk your entire career with a single 'fix everything' commit that somehow breaks three unrelated features
The real tragedy here isn't the 1049 deletions - it's that when this inevitably breaks production at 2 AM, git bisect will be about as useful as a chocolate teapot. Meanwhile, they probably have 47 quicksaves from the last boss fight, each meticulously named with timestamps. Priorities: a developer's guide to risk management where production code gets less backup strategy than a Skyrim playthrough
Games enforce atomic saves; Git lets us batch Big Bangs into 'some changes' until bisect reveals the crime scene
I quicksave every five minutes in games, but at work I drop a +647/−1049 'some changes' - apparently “atomic” describes the blast radius, not the commit
Peak senior move: one "some changes" commit bundling a schema migration, refactor, and dependency bump - expertly tuned to defeat git bisect and any chance of a sane code review