Jargon programmers

I came across Stackoverflow.com on an interesting topic with a question about the new in programming jargon. I offer here a selection of the most interesting expressions.

Egyptian Operator Brackets

if (a == b) {
  printf("hello");
}



Fear Driven Development

Fear-driven development — when project management only adds fuel to the fire and puts undue pressure on developers.

Hope Driven Development

Hope-driven development - development in a long unplanned cycle with the hope that everything will work in the release

Rob Busack: Real Waterfall Model.

Named after the annual Fast Development Weekend named Rob Busack .

Refactoring

refactoring - obtaining completely unsupported code by making small changes to high-quality and well-designed code.

Code - Baklava

Layered Layered Code

Press harder / Wrong finger / hold the mouse correctly

The developer’s reaction to the claims of testers that something does not work when using one of the input devices.

Tester: Module X does not work correctly
Developer: Show the steps of testing
Tester: I touched it, then ... oh wait, now everything works.
Developer: With which finger do you touch the screen?
Tester: Index finger
Developer: You must have used the wrong finger before.
Tester: Yes ... perhaps ..

String typing (Stringly typed vs strongly typed)

Using strings as parameters where more suitable types can be found

Natural selection

Replacing someone else's code with your own.

frAGILE

frAGILE - getting people crazy by misusing Agile methodologies

Project Manager: Let's use the Agile methodology!
Developer: Okay. I will do the minimum to achieve the necessary business functionality.
Project Manager: Great!
Developer: We can do refactoring after other parts of the system are built. Now this is not very important.
Project Manager: Good. We must not do more than necessary

Later in the project ...

Developer: We need refactoring because the code is unsupported

... then ...

Project Manager: Choosing excuses for not deploying:

• We can do it a bit later
• If everything works, why change something?
• We don’t have time for this “refactoring”
• I promise we will do it later

Bottom line: The developer suffers from an increasing incoherent spaghetti code and nobody cares.

CTO: Agile is disgusting! We will never use it! A model of a waterfall rules!

Boss build

Creating a special version of the product release to run on the Boss computer. For example, the boss build may include an endless list of specific fonts, colors, sizes, and layouts of controls that change every few days.

James Bond Interface

The contract is very well defined and documented, but in reality, nothing has been implemented.

Classtrophobia

Refusal from an object-oriented approach with obvious need and the possibility of its use.

Very Oriented Programming (OOP)

The use of five levels of classes, when you can do only one

Bukazoid documentation pattern

The entire description is useless and does not answer any of the questions to the code. Instead of bucasoids, you can use any non-existent word, in Russian, it seems, butyavoks are most suitable.

/**
* Bukazoid manager is a manager to manage bukazoids.
*/
public class BukazoidManager extends SomeOtherClass {
...
}



Perkov Method

The Perkov Method is a programming style based on comments in the form of pseudo-code and the assumption that someone who will do code reviews will implement the missing functionality. In the final stage, comments can be 4 times more detailed than is necessary in the implementation. Example: usual implementation of Hello World:

class Program
{
  static int Main(string[] args)
  {    
    Console.WriteLine("Hello World");
  }
}



Implementation by the Perkov method:

class Program
{
  static int Main(string[] args)
  { 
    // at this point the program really should be outputting text to the
    // console. we must take into account 78 character maximum line length
    // and ensure that we use Environment.NewLine for line endings.
    // ideally should provide multi-region language support and UTF-8 /
    // UTF-16 encoding.
  }
}



Marketing bytes

Bytes measured as factors of 1000

Ship in a bottle

The API is simplified to such an extent that it is desperate to use it.

Ping Pong Development Methodology

Let users be testers, give them a raw product and accept a portion of bugs.

Darwin Programming / Experimental Programming

Changing the code (usually random) without understanding the meaning of the changes until it works. For example, replacing increment with decrement.

TDDD: Technical Debt-Driven Development

(* fixed by habruiser dale ) Development driven by technical debt. That is, when the developer constantly puts off fixes and improvements in the code for later.