We still live in an era where most of the computer behavior is dictated by human generated code.
One of biggest errors one can make is to assume that such code is bullet proof based of the myths that people take for granted e.g.: works on my machine, it has 100% test coverage, and such.
is it still working?
The impact of the assumption that once the code ran, it will work forever is the unawareness of unexpected behaviour, which, to some extend, should be already covered by current testing methodologies, considering that code already doesn’t work 100% of the time.
A quick search on Google for “software bug” demonstrates how badly we fail on proving the quality of our code, from a low-level kind of bug such as Meltdown up to self-driving car issues.
Writing code for professional usage presents a very overwhelming challenge:
How does one ensure its code works the way it was designed to?
Innumerous answers to that question emerged over the course of the software development history. From…
