Look at how they prescribe drugs for the side effects of other drugs. Imagine coding a software patch to fix a bug introduced by another patch.
Look at how they prescribe drugs for the side effects of other drugs. Imagine coding a software patch to fix a bug introduced by another patch.
Imagine a world in which you got paid for patches instead of being paid by the hour. Patches on patches would likely proliferate.
The two systems aren't remotely comparable in complexity.
If you get cancer, the treatment you get can cause very many side effects which in turn can potentially be alleviated by other type of medicine. What would your suggestion be? Not to treat the patient at all?
This happens all the time.
As a support engineer.... Is this not common? Cause dear lord does my (large corporate entity that shall not be named) do this ALL THE TIME.
Most recent was a set of about 5 consecutive patches for shitty patches.
Send help.
But this is very common! Far from mocking my fellow developers, I'll be the first to admit I've been guilty of this many times.
You have the self inflated ego of a psychopath if you think this is true. This comment is the living embodiment of the Dunning-Kruger effect.