So when faced with spaghetti code I tend to rewrite, comment out old code with a detailed explanation as to the reasons, and then a well commented re-implementation of the original solution.

This then serves as a reference to myself collaborators and original author as to why the original implementation was messy, how and why my code improves on the original code.

Hopefully others then learn from myself and can pick up my style, which although I try to practice good patterns I will openly admit can often become obfuscated to new collaborators.

The only time I see the Spaghetti cycle is when code is re-written by a novice programmer, who might implement some good changes but often creates as much of a mess as the original author.

One of the beauty’s of modern code is that it is no longer the complicated mash of op codes and assembly so there is so much more scope for the code to be considerably optimized, in terms of legibility.

Well happy coding people. :)

So, I think you mistaken or published wrong link.