The Bug, an endangered specy
Learn how to code is really difficult… But fix a bug is even more harder ! But do you know why ?
Each of you has already experimented a bug. The true story is that this word comes from the very beginning of the informatics, when real bugs were nested in the computer bays and induced treatment errors.
Today, these small animals are just a concept that refer an unexpected behavior. Unfortunately, this word covers much more than a single meaning and is one of the cause of the digital crack ! Let me explain why.
The bug is an error, but of whom?
In the commun sense, the bug is an error thrown by the computer. If this is true regarding the origin of the word “bug”, it is no longer the case nowadays. 99,9% of the bugs are actually errors made by the “coder”. Indeed, the program designer has formally introduced the bug since a machine, except very extraordinary cases, does not make any error. The computer only executes the procedure that has been defined explicitly or implicitly by the algorithm of the developer.
The most annoying part of the bug is that is introduced by the designer without any intention to do it. By this way, the bug can be nested in several places that you will be not able to track:
- The first well-known bug is hidden in the famous « oups I didn’t expect such a value as an entry ». In this case, the program retrieves a data that it is able to deal with. For instance, if you ask your user to enter its age and this user enters the date of birth. Just imagine that you need to compare this “age” as date of birth with the majority age, you will encounter some troubles ! At this stage, you can easily incriminate the user or the UX designer for this misunderstanding