The Hypocrisy of Saving: Gaming vs. Git Commits
Description
A screenshot of a tweet from user Amy Nguyen (@amyngyn). The tweet presents a humorous contrast in behavior. The first line reads: 'me playing video games: save every five minutes'. The second line reads: 'me writing code: git commit -am "some changes" (+647, -1049)'. The profile picture for the tweet shows a quokka. The meme highlights a common and relatable hypocrisy among developers: being extremely cautious and saving frequently in a low-stakes context like a video game, while being reckless in a professional context by making a massive, multi-faceted code change (over 1700 lines affected) and summarizing it with a completely unhelpful git commit message, 'some changes.' This practice goes against version control best practices, which favor small, atomic commits with descriptive messages for maintainability and easier code reviews
Comments
7Comment deleted
In gaming, we save often to avoid losing a few minutes of progress. In coding, we avoid committing for hours to avoid admitting to ourselves that the last 1,700 lines of changes were a terrible idea
I quick-save before every jump in Celeste, yet my “trunk-based” workflow is a single Friday push to main: git commit -am "oops_more_fixes" (+1,842 −1,309). Seniority just means I’ve rebranded living dangerously as CI velocity
The irony of meticulously saving game progress every 5 minutes while casually obliterating git history with 1600-line atomic bombs labeled 'some changes' - because apparently, losing 30 seconds of gameplay is more catastrophic than making the next developer contemplate career changes during code review
The classic developer paradox: religiously quicksaving before every minor decision in a game, but casually yeeting 1,696 lines of changes into a single commit with a message that would make any code reviewer weep. At least when you rage-quit the game you can reload; when you rage-quit that PR review, you're archaeology-ing through git blame for the next three sprints trying to figure out what 'some changes' actually broke
Games: save every five minutes; Git: a single “some changes” (+647/-1049), turning code review into theology, rollback into disaster recovery, and git bisect into archaeology
Save checkpoints every boss fight, but ship a single "some changes" with +647/-1049 - aka the diffstat that turns code review into archaeology and makes git bisect weep
'Some changes' (+647/-1049): the commit message that turns code review into an archaeological dig