It seems to me the issue in this article wasn't caused by soft deletes, it was caused by a botched migration from soft deletes to the history table method the author is recommending. Blaming the issue on soft deletes completely misses the actual root cause.