Stack Overflow In asked readers for possible new slang terms, or invented by them or others in his circle (friends, colleagues and other people nearby). As expected, the result is mostly a collection of jokes of the guild, some are pretty horny.
reproduce a few that I especially liked. Not translate because some lose their meaning, and also because I do not want nothing, nothing (as you see, try to be be honest). Equal to another if you like to translate and put them in your blog or wherever.
Well, are these:
- Bugfoot : A bug That isn't reproducible and has been sighted by only one person. See "Loch Ness Monster Bug".
- Hindenbug : A catastrophic data-destroying bug. Oh, the humanity!
- Heisenbug / Schrödingbug : A bug that disappears or alters its characteristics when an attempt is made to study it.
- Higgs-Bugson : A hypothetical bug predicted to exist based on a small number of possibly related event log entries and vague anecdotal reports from users, but it is difficult (if not impossible) to reproduce on a dev machine because you don't really know if it's there, and if it is there what is causing it.
- Unicorny : An adjective to describe a feature that’s so early in the planning stages that it might as well be imaginary. This one comes from Rails Core Team member Yehuda Katz, who used it in his closing keynote at last year’s Windy City Rails to describe some of Rails’ upcoming features.
- Drug Report : A bug report so utterly incomprehensible that whoever submitted it must have been smoking crack.
- Yoda Conditions : The act of using if (constant == variable) instead of if (variable == constant) . It’s like saying “If blue is the sky”.
- IRQed : Annoyed by interruptions. Pronounced like and has a similar meaning to “irked”.
- Reality 101 Failure : The program (or more likely feature of a program) does exactly what was asked for, but when it’s deployed it turns out that the problem was misunderstood and the program is basically useless.
- Refuctoring : The process of taking a well-designed piece of code and, through a series of small, reversible changes, making it completely unmaintainable by anyone except yourself. It’s job security!
- Duck : A feature added for no other reason than to draw management attention and be removed, thus avoiding unnecessary changes in other aspects of the product. ( Más info y un ejemplo real ).
- Exception Handling Pokemon: For When You just gotta catch 'em all!
can see that the situations described are very real, at least I've seen most of them.
strikes me especially Heisenbug / Schrödingbug . These bugs are among the bastards, because everything indicates that regardless of what every state (forgive the redundancy), the bug will be there or not, and what is worse: At the end of a kitten dies (or not).
also the Higgs-Bugson , because the Higgs boson is called, metaphorically, "God particle" because it could be this bug called "the bug of God": It seems that you are laughing at you (and that's fucking annoying). Via
Global Nerdy
reproduce a few that I especially liked. Not translate because some lose their meaning, and also because I do not want nothing, nothing (as you see, try to be be honest). Equal to another if you like to translate and put them in your blog or wherever.
Well, are these:
- Bugfoot : A bug That isn't reproducible and has been sighted by only one person. See "Loch Ness Monster Bug".
- Hindenbug : A catastrophic data-destroying bug. Oh, the humanity!
- Heisenbug / Schrödingbug : A bug that disappears or alters its characteristics when an attempt is made to study it.
- Higgs-Bugson : A hypothetical bug predicted to exist based on a small number of possibly related event log entries and vague anecdotal reports from users, but it is difficult (if not impossible) to reproduce on a dev machine because you don't really know if it's there, and if it is there what is causing it.
- Unicorny : An adjective to describe a feature that’s so early in the planning stages that it might as well be imaginary. This one comes from Rails Core Team member Yehuda Katz, who used it in his closing keynote at last year’s Windy City Rails to describe some of Rails’ upcoming features.
- Drug Report : A bug report so utterly incomprehensible that whoever submitted it must have been smoking crack.
- Yoda Conditions : The act of using if (constant == variable) instead of if (variable == constant) . It’s like saying “If blue is the sky”.
- IRQed : Annoyed by interruptions. Pronounced like and has a similar meaning to “irked”.
- Reality 101 Failure : The program (or more likely feature of a program) does exactly what was asked for, but when it’s deployed it turns out that the problem was misunderstood and the program is basically useless.
- Refuctoring : The process of taking a well-designed piece of code and, through a series of small, reversible changes, making it completely unmaintainable by anyone except yourself. It’s job security!
- Duck : A feature added for no other reason than to draw management attention and be removed, thus avoiding unnecessary changes in other aspects of the product. ( Más info y un ejemplo real ).
- Exception Handling Pokemon: For When You just gotta catch 'em all!
can see that the situations described are very real, at least I've seen most of them.
strikes me especially Heisenbug / Schrödingbug . These bugs are among the bastards, because everything indicates that regardless of what every state (forgive the redundancy), the bug will be there or not, and what is worse: At the end of a kitten dies (or not).
also the Higgs-Bugson , because the Higgs boson is called, metaphorically, "God particle" because it could be this bug called "the bug of God": It seems that you are laughing at you (and that's fucking annoying). Via
Global Nerdy
0 comments:
Post a Comment