The Eternal Question: Bug or Feature?
Description
A classic two-part meme format. The top section contains text: 'Customer: Is this a bug or a feature?'. Below this, under the label 'Devs:', is a reaction image. The image is a still frame of the character Shrek from the movie of the same name. He has a thoughtful, slightly smug expression on his face and is gesturing with his hand as if conceding a point. The caption at the bottom of the image reads, 'Good question.' The humor lies in the developers' non-committal and slightly mischievous response. It perfectly captures the ambiguous nature of some software behaviors, which could be unintended errors (bugs) or could be spun as undocumented, intentional functionality (features), depending on the perspective and the effort required to fix them. The meme resonates with any developer who has had to navigate this delicate conversation with stakeholders
Comments
8Comment deleted
It's a feature if the product manager can sell it. It's a bug if it wakes someone up at 3 AM. Until then, it's just 'unexpected behavior'
If support can bill it and QA can’t reproduce it, congratulations - your P1 bug just got promoted to a strategic feature
The real answer depends on whether the Jira ticket was created before or after the code was deployed to production
It's a bug until enough enterprise customers build workflows on it - then it's a feature with an SLA and a deprecation committee
When a customer asks 'Is this a bug or a feature?', the correct answer depends entirely on whether it's documented in the spec, mentioned in the retrospective, or already shipped to production. Senior engineers know this is actually a philosophical question about the nature of intentionality in software - if nobody wrote a test for it, did the behavior ever truly exist? The real answer: 'It's a feature until the post-mortem, then it becomes a learning opportunity.'
In enterprise triage, it's a feature when PM can retrofit acceptance criteria before the postmortem; it's a bug when SRE has a flame graph and a PagerDuty ticket
Features are bugs with a spec doc; the rest get stack traces in prod
Our classifier is cost-center aware: label=bug when Support pays; label=feature when it helps Product hit an OKR; else default=“works as designed” with an updated spec