Reminds me the law of entropy and conservation of bug counts...
So looked up some other software development laws. in case being in need of optimism too:
Years of observing programs in their natural environment have shown that
"Bugs will appear in one part of a working program when another 'unrelated' part is modified."
So with v17 introducing facilities looking forward to buggy inventory!
"If debugging is the process of removing bugs, then programming must be the process of putting them in." -- E. W. Dijkstra
Hm... I see, need to keep that programming part to minimum...
Also don't overdo it with diligence, ok, because
"It is twice as difficult to debug a program as to write it. Therefore, if you put all of your creativity and effort into writing the program, you are not smart enough to debug it."
In any case, resistance is futile, as it eventually boils to
"Program complexity grows until it exceeds the capability of the programmer who must maintain it."
But don't worry, be flexible. Closing any inconvenient talking dead issues with
"It’s not a bug, it’s a forthcoming feature!"
Simply stretching A. C. Clarke's
"Any sufficiently advanced bug is indistinguishable from a feature." -- R. Kulawiec
All in all, if everything else fails, there is always at least one solution for all the problems implied in the simple truth
"The last bug isn't fixed until the last user is dead." -- S. Markowitz
Helped me.
Edit: credit.
