Nueva jerga en programación
En Stack Overflow preguntaron a los lectores por posibles nuevos términos de la jerga, bien inventados por ellos o por otros dentro de su círculo (amigos, compañeros y otra gente cercana). Como era de esperar, el resultado es mayormente una colección de chistes del gremio, algunos son bastante cachondos.
Reproduzco unos cuantos que me gustaron especialmente. No los traduzco porque algunos perderían su significado, y también porque no me apetece nada-nada (como veis, trato de ser ser sincero). Igual a otro sí le apetece traducirlos y ponerlos en su blog o donde sea.
Bueno, son estos:
- 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).
- Pokemon Exception Handling: For when you just gotta catch ’em all!
Podéis ver que las situaciones descritas son bastante reales, yo al menos he presenciado la mayoría de ellas.
Me llama la atención especialmente el Heisenbug/Schrödingbug. Estos bugs son de los más cabrones, porque todo indica que independientemente de lo que todo indique (valga la redundancia), el bug estará ahí o no estará, y lo que es peor: Al final muere un gatito (o no).
También el Higgs-Bugson, porque al bosón de Higgs se le llama -metafóricamente- "la partícula de Dios", y a este bug se le podría llamar "el bug de Dios": Parece que se esté riendo de ti (y eso es jodidamente irritante).
Vía Global Nerdy
Reproduzco unos cuantos que me gustaron especialmente. No los traduzco porque algunos perderían su significado, y también porque no me apetece nada-nada (como veis, trato de ser ser sincero). Igual a otro sí le apetece traducirlos y ponerlos en su blog o donde sea.
Bueno, son estos:
- 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).
- Pokemon Exception Handling: For when you just gotta catch ’em all!
Podéis ver que las situaciones descritas son bastante reales, yo al menos he presenciado la mayoría de ellas.
Me llama la atención especialmente el Heisenbug/Schrödingbug. Estos bugs son de los más cabrones, porque todo indica que independientemente de lo que todo indique (valga la redundancia), el bug estará ahí o no estará, y lo que es peor: Al final muere un gatito (o no).
También el Higgs-Bugson, porque al bosón de Higgs se le llama -metafóricamente- "la partícula de Dios", y a este bug se le podría llamar "el bug de Dios": Parece que se esté riendo de ti (y eso es jodidamente irritante).
Vía Global Nerdy
