Bug Debug Glitch

Now this term is used more and more often, even outside the geek context especially by the zeta generation to indicate something that does not work as it should.
The term bug, in the context of computer programming, is a problem that leads to the malfunctioning of a software. A program that has more than one error is defined buggy, while its arrangement is called bug fixing.

The origin of this name is really curious. Literally, from English, it means “insect”.
The first computer malfunction was in 1947 when a computer stopped working. After extensive research, the cause was finally found: a small moth was wedged between the relays of the computer, preventing the correct use. The moth was removed, glued with scotch tape into the computer log, and the annotation “First actual case of bug being found” was added.

When a bug is discovered it’s necessary to modify the part of the source code that causes the malfunction and then release a new version of the program or a patch, that is, an overwrite or rewrite of that portion.
The resolution times depend on many factors such as the program, the type of error and the programmer. If you find a bug, the best way to get it fixed is to provide as much information as possible so that people can play it.
Bugs can be grouped into two types: semantic and runtime. Semantic or logical errors are those made during design. If something is wrong at this stage, especially in basic algorithms, errors will spread systematically during development, generating problems or not working at all, even if the code is syntactically correct. In this case, therefore, it is not spelled wrong, but behaves incorrectly.

The other errors, called runtime errors, occur during the execution of the program and occur due to particular input values or due to incorrect memory management. These bugs are the most common in video games in how many in their development is used the logic of event programming according to which, the flow of the program and the instructions to be executed, are linked to the commands that the player gives and not by pure programming choices.

The bug only occurs for a small group of people and its priority is very low. Sometimes a bug occurs only in specific cases and without serious repercussions, in this case it might be uneconomic for the company to spend a lot of resources to fix it.

The term glitch (literally “slipping”) identifies a sudden and short-lived peak error of a signal. It’s therefore a small disturbance in the operation of the program and occurs quite often when graphics are loaded only partially. Most glitches are fixed, with a patch. Alternatively, in some cases even a graphic card update can solve the problem if the glitch is traceable to software that is not recent.
Be careful though not to confuse it with the bug! A glitch is not a programming error, but a strange response to a design choice defined during development. However, it’s possible that some glitches may trigger bugs.

Be careful though not to confuse it with the bug! A glitch is not a programming error, but a strange response to a design choice defined during development. However, it’s possible that some glitches may trigger bugs.

The term debugging refers to many different elements, but more literally it means removing bugs from code. Since there are so many different bugs, there are also many ways to do this. Often a debugger is used, that is, a development tool that connects to the running app and allows you to check the code to understand where the error is located.
Debugging therefore leads to the removal through changes to the source code of the error and is a very delicate procedure, especially in the phase of modification, because it’s necessary to maintain the structure of the software, without tampering with its key points, but go to intervene by removing the bug.