Reporting my messy pull request as garbage using Facebook options
Description
The meme is split into two parts. The top photo shows a roadside scene with a broken couch and an enormous pile of scattered trash - plastic bags, cardboard, cans - sprawled across grass and pavement under a sunny sky. The bottom half mimics Facebook’s “What’s going on?” report dialog, listing four radio-button choices: “It’s annoying or not interesting,” “My PR is in this photo and I don’t like it” (this option is selected), “I think it shouldn’t be on Facebook,” and “It’s spam.” By equating the garbage heap with a developer’s pull request (PR), the meme pokes fun at code reviews where contributors feel their own code is embarrassingly messy - akin to public trash - highlighting quality, technical debt, and review pain points familiar to engineers who live in Git workflows
Comments
6Comment deleted
My “quick refactor” PR crossed 12k LOC - GitHub hid the diff, the CI OOM-killed itself, and Facebook politely offered a “report as litter” button; apparently the only garbage collection left is municipal
After 15 years of explaining why we need refactoring time, I've learned to just mark it as 'performance optimization' and watch it sail through approval
This is what happens when your CI/CD pipeline has more 'continuous' than 'integration' - someone force-pushed to main at 4:59 PM on Friday, the approval bot was down, and now your carefully crafted PR is sitting in production next to that regex someone copy-pasted from Stack Overflow in 2019. At least the garbage collector will eventually get to it... right?
This pile has better encapsulation than my last PR - at least the trash bags contain their leaks
PR titled “minor cleanup” with a diff of couch, fridge, 4k files of formatter churn, a surprise schema migration, and vendored node_modules - where’s GitHub’s “report illegal dumping” button?
Nothing says minor cleanup like a 12k-line PR with lockfile churn, vendored node_modules, and a request for quick review before EOD