Hot answers tagged jargon
I'll suggest a new one, Sleeper Cell. Seems apt to me. A sleeper cell refers to a cell, or isolated grouping of sleeper agents that belong to an intelligence network or organization. The cell "sleeps" (lies dormant) inside a target population until it receives orders or decides to act
A Duck From http://www.codinghorror.com/blog/2012/07/new-programming-jargon.html: 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.
It's simply referred to as inefficient. Efficiency/performance: the amount of system resources a program consumes (processor time, memory space, slow devices such as disks, network bandwidth and to some extent even user interaction): the less, the better. This also includes correct disposal of some resources, such as cleaning up temporary files and lack of ...
I and a few others I have worked with call those a Timebomb. I know that this would give it a dual meaning; often "timebomb" is used for a piece of malicious code put in by a programmer that is set to go off at a certain point in time. However, when no circumstances seem to change other than the time (as you said had happened with your bug) then "timebomb" ...
Actually in manufacturing (and quality assurance) there is something called a Red Rabbit Test (aka Red Herring) that refers to putting a known bad part into the machine or process and making sure it's detected. Some automated machines have automatic cycles (typically once per shift) where it prompts the operator to load the "red rabbit" part and then it ...
I think you've hit on an important question. We don't have good words to describe unnecessary computation. One word is "bottleneck". That seems to describe something localized, that traffic has to get through, and limits the speed. The trouble is, in decades of performance tuning, I've found and fixed numerous problems, and none of them fit that image. ...
Martin Fowler's Refactoring book identifies long methods as a code smell, with the Extract Method refactor being a solution. I think it could also be considered a derivative of the Single Responsibility Principle. Applying it at the method level can make unit-testing much easier, since you don't have to worry about testing multiple results from a single ...
I call these sorts of bugs "Submarine Bugs", sort of like "Submarine Patents", something that is present, but unseen until it surfaces. The other kinds of bugs mentioned, like Heisenbugs, and Schrodingbugs are quite different in that they are bugs that you are know are there, but change during observation.
A proxy, in its most general form, is a class functioning as an interface to something else. The proxy could interface to anything: a network connection, a large object in memory, a file, or some other resource that is expensive or impossible to duplicate. - Wikipedia In the very context you quote, it means that said methods serve to ...
A dormant bug - Heraldic, so dormant bug as opposed to a rampant bug that is right now affecting EVERYTHING. Also has a nod to dormant and active volcanoes and super volcanoes like Yelowstone park.. (image credit, Wikicommons, http://commons.wikimedia.org/wiki/File:Lion_Dormant.svg)
According to wikipedia they're called "upvalues". A closure allows a function to access variables outside its immediate lexical scope. An upvalue is a free variable that has been bound (closed over) with a closure. The closure is said to "close over" its upvalues. Although it's probably better to wrongly call them private variables so people will ...
Seems like my professors called it bebugging or fault seeding. The idea is that if you wanted to estimate the population of something like fish in a lake, you could catch some, tag and release them, give them time to assimilate randomly with the other fish, then estimate the population based on how many tagged fish you catch later. This search link finds a ...
The classifications I've always known are Web Development Desktop Development Mobile Development Embedded Systems Development Database Development (Stored Procs, etc.) Client-Server Development (Not used as frequently as it once was)
I still see quite a few ads for Desktop Application Development. I think you might get more play if you specify the platform - Windows Application Development or OSX Application Development, for example, along with the languages (eg, C++) and libraries/frameworks (eg, Qt), so something like: Developed applications for Windows using C++ in Qt 4.5
There was a special terminology that just evolved at a company I used to work out. Many of the developers since have moved on and seemingly have spread the language. Pixies: when things mysteriously break, seeming with(out) reason. Fairies: when things that were once broken mysteriously fix themselves, seeming with(out) reason i.e. "The damn pixies are at ...
Sometimes a quick and temporary fix is applied to restrict an application to deal with a serious bug. It's a temporary patch, and not a fix. When the fix is a priority, it is often fast tracked and released immediately after the temporary solution. This could typically be called a fast follower. Sadly, I think this is more a case of the Pointy Haired ...
There are a variety of terms depending on what you're doing. In order of their chances of successful recovery these are: 1. Move to trash You just move the file into a generic "recycle bin". You can fish it out later if you need to. Not secure at all. Perhaps this would be "security by obscurity" if you didn't know where the trashcan was. 2. Delete This ...
The term that I prefer is Negatively optimised code. Negatively optimised code that forces the processor and/or I/O systems to jump through a number of programmer-created hoops that in no way change the business correctness of the code. Negatively optimised code may be created for any number of reasons. Some good and some bad. Sometimes even following ...
Non - Scalable – I recently ran into this issue where a lot of code was run doing nothing on a set of data under most circumstances. This worked fine dealing with 200 rows of data but when dealing with 20,000 rows of data the time to loop and inspect unchanged data took to long. Do not write Non-Scalable code.
It can be described as code that has a big overhead, much is done in order to attain its purpose. From Wikipedia: In computer science, overhead is any combination of excess or indirect computation time, memory, bandwidth, or other resources that are required to attain a particular goal. It is a special case of engineering overhead. I have a quarrel with ...
"Surplus Runtime Memory Consumption" is the expression what would describe the situation you have described in your question. When a large fraction of the code is running (when not needed), it obviously occupies large fraction of memory unneccsarily. As a consequence, surplus or extra amount of memory is consumed that can be avoided by via good program ...
It is the Detonator pattern : Detonator The Detonator is extremely common, but often undetected. A common example is the calculations based on a 2 digit year field. This bomb is out there, and waiting to explode!
"Fast follower" is a code word for we have already failed because we don't take any calculated risks on implementing our own innovative ideas. It means we won't do anything until someone else has succeeded in doing it and by then it is too late in the game. I worked for a billion dollar a year company that used to espouse this as a virtue. Guess what they ...
I forget where I read it, I think it was the Rails company Thoughtbot but the basic idea was to use "Sign" for everything so that there are three actions always: Sign In Sign Out Sign Up This nomenclature makes sense because the basis for authentication is a logbook, so you "sign in" when you enter and "sign out" when you leave.
Only top voted, non community-wiki answers of a minimum length are eligible