Bugs
Post #3519 · source on Telegram
The Age-Old Question: Bug or Feature?
Description
A classic two-part meme format. The top section contains text on a white background. It presents a dialogue: 'Customer: Is this a bug or a feature?' followed by 'Devs:'. The bottom section is a screenshot of the character Shrek, who has a thoughtful, slightly smug expression on his face, with the subtitle 'Good question.'. The meme humorously captures a common and often ambiguous situation in software development where an unexpected behavior could be interpreted as either a flaw (bug) or an intentional, albeit poorly documented, aspect of the system (feature). For experienced developers, this is a deeply relatable scenario that touches on themes of legacy code, technical debt, and the subtle art of managing client expectations
More like this
More like this in Bugs →
Use J and K for navigation
Comments
12Comment deleted
The answer to 'Is it a bug or a feature?' is determined by a single variable: the number of days left before the release date
Schrödinger’s requirement: QA logs it as a P1, sales demos it as differentiation, and by the time I’m paged, it’s mysteriously become “phase-one architecture.”
The real answer depends on whether we've already invoiced for it and how close we are to the quarterly board meeting
The Schrödinger's code phenomenon: until you check the original requirements doc (which doesn't exist), the behavior exists in a superposition of both bug and feature states. Senior engineers know the correct answer is always 'Good question' - it's not evasion, it's strategic ambiguity management while you frantically search git blame to see if drunk-you from 2 AM three months ago left any comments explaining this 'creative interpretation' of the spec
In our org, 'bug vs feature' is a quantum state collapsed by whoever files the Jira - Sales collapses to 'expected behavior'; SRE collapses to SEV-1
We classify behavior by who found it: if Product demoed it, it’s a feature; if PagerDuty did, it’s a bug
In microservices, it's always a 'feature' of the upstream service - until you own the whole stack
Classic :) Comment deleted
😂😂😂😂😂😂 Comment deleted
Actually in reality if you don't mention something they can say its a bug because its not in the docs and can refund or get money back for "non documented" behavior. Comment deleted
Oh really?! First time heard this Comment deleted
If the software has bugs that you meantion and they accept it, they can't do shit about it except waiting for you to give them an update Comment deleted