Bagotron
The world of software is the world of bugs. Soft is born to overcome the bugs that came before it. Software lives and develops in the fight against the bugs that are in it. The software dies from bugs that the software going to replace it will fight with.
Software and bugs are inseparable, like Yin and Yang, like light and dark, like life and death. Creating software, you create bugs. While bugs are found in the software, he lives. If there are no bugs in the software, then no one is looking for them anymore. So, software is dead.
Starting a project, you open a new world for bugs.
Writing down the requirement, you create food for the bug.
By developing an algorithm, you build a dwelling for the bug.
By writing an operator, you breathe life into a bug.
By killing a bug, you clear a place for new bugs.
')
What would a manager in a world without bugs be? Nothing. For all his science is created only to overcome the bugs. The stupid manager boasts of his imaginary power and believes that the project can be completed by releasing software without bugs. The first project will bring down his arrogance and add mind. If the manager proceeds with this faith to the second project, then he becomes the last one. Such a manager loses power forever.
What would a coder in a world without bugs be? Nothing. For if software is possible without bugs, then coding would be entrusted to machines.
Coder creates bugs. Coder kills bugs, giving rise to a host of new bugs. Coder thinks he has been given authority over the bugs, but this authority is illusive. Ensuring the eternal circulation of bugs, the coder only fulfills its purpose, not realizing it.
The coder who realizes his purpose becomes a Hacker, or enlightened.
The hacker breaks the vicious circle, stopping to kill the bugs. From now on he is not a flock, but a shepherd.
Like a tester, Hacker constantly searches for bugs, but searches for them in such depths that the tester does not reach.
Having found the bug, Hacker begins to magnify it. First of all, Hacker gives the name of the bug, but does not communicate it to the world, because the time has not yet come. The hacker surrounds the bug with care and love, nurtured around him a special software, called an exploit, and a thousand times strengthened the power of the bug. Only after that Hacker reveals the name of the bug, but not to everyone, but only to other Hackers. United by a common goal, Hackers are looking for incarnations of the bug in all corners of the world and exploit to give them new power. And then, finally, the bug appears before the world in all its formidable glory and greatness, and its name strikes terror in users.
What would a tester be in a world without bugs? Nothing. For if there are no bugs, where does the tester come from?
Testers, more than anyone else, owe their existence to the bugs. Grateful, they became ministers in the Temple of the Bag. Testers are looking for bugs. Testers give bugs names. Testers look after bugs, accompanying them all the way from status to status. Testers mourn bugs, escorting them to the status of eternal rest.
What would be a user in the world without bugs? The same as it is in this world is an empty place.
So, what is a bug for a manager? Humility of pride and a storehouse of wisdom.
What is a bug for the coder? The fate and the path to enlightenment.
What is a bug for a hacker? Revelation and source of vitality.
What is a bug for the tester? Deity and meaning of existence.
Finally, what is a bug for the user? The reality of the world in which he stagnates.
Cross-topic from a personal blog greesha.ru
Software and bugs are inseparable, like Yin and Yang, like light and dark, like life and death. Creating software, you create bugs. While bugs are found in the software, he lives. If there are no bugs in the software, then no one is looking for them anymore. So, software is dead.
Starting a project, you open a new world for bugs.
Writing down the requirement, you create food for the bug.
By developing an algorithm, you build a dwelling for the bug.
By writing an operator, you breathe life into a bug.
By killing a bug, you clear a place for new bugs.
')
What would a manager in a world without bugs be? Nothing. For all his science is created only to overcome the bugs. The stupid manager boasts of his imaginary power and believes that the project can be completed by releasing software without bugs. The first project will bring down his arrogance and add mind. If the manager proceeds with this faith to the second project, then he becomes the last one. Such a manager loses power forever.
What would a coder in a world without bugs be? Nothing. For if software is possible without bugs, then coding would be entrusted to machines.
Coder creates bugs. Coder kills bugs, giving rise to a host of new bugs. Coder thinks he has been given authority over the bugs, but this authority is illusive. Ensuring the eternal circulation of bugs, the coder only fulfills its purpose, not realizing it.
The coder who realizes his purpose becomes a Hacker, or enlightened.
The hacker breaks the vicious circle, stopping to kill the bugs. From now on he is not a flock, but a shepherd.
Like a tester, Hacker constantly searches for bugs, but searches for them in such depths that the tester does not reach.
Having found the bug, Hacker begins to magnify it. First of all, Hacker gives the name of the bug, but does not communicate it to the world, because the time has not yet come. The hacker surrounds the bug with care and love, nurtured around him a special software, called an exploit, and a thousand times strengthened the power of the bug. Only after that Hacker reveals the name of the bug, but not to everyone, but only to other Hackers. United by a common goal, Hackers are looking for incarnations of the bug in all corners of the world and exploit to give them new power. And then, finally, the bug appears before the world in all its formidable glory and greatness, and its name strikes terror in users.
What would a tester be in a world without bugs? Nothing. For if there are no bugs, where does the tester come from?
Testers, more than anyone else, owe their existence to the bugs. Grateful, they became ministers in the Temple of the Bag. Testers are looking for bugs. Testers give bugs names. Testers look after bugs, accompanying them all the way from status to status. Testers mourn bugs, escorting them to the status of eternal rest.
What would be a user in the world without bugs? The same as it is in this world is an empty place.
So, what is a bug for a manager? Humility of pride and a storehouse of wisdom.
What is a bug for the coder? The fate and the path to enlightenment.
What is a bug for a hacker? Revelation and source of vitality.
What is a bug for the tester? Deity and meaning of existence.
Finally, what is a bug for the user? The reality of the world in which he stagnates.
Cross-topic from a personal blog greesha.ru
Source: https://habr.com/ru/post/39081/
All Articles