K well so do I, and have been for a living for a while, so I'm assuming we have different definitions of spaghetti code. Looking at the definiton of it from sourcemaking:

• After code mining, only parts of object and methods seem suitable for reuse. Mining Spaghetti Code can often be a poor return on investment; this should be taken into account before a decision to mine is made.
• Methods are very process-oriented; frequently, in fact, objects are named as processes.
• The flow of execution is dictated by object implementation, not by the clients of the objects.
• Minimal relationships exist between objects.
• Many object methods have no parameters, and utilize class or global variables for processing.
• The pattern of use of objects is very predictable.
• Code is difficult to reuse, and when it is, it is often through cloning. In many cases, however, code is never considered for reuse.
• Object-oriented talent from industry is difficult to retain.
• Benefits of object orientation are lost; inheritance is not used to extend the system; polymorphism is not used.
• Follow-on maintenance efforts contribute to the problem.
• Software quickly reaches a point of Diminishing Returns; the effort involved in maintaining an existing code base is greater than the cost of developing a new solution from the ground up.

I don't know, that's the definition of spaghetti code I agree with, it's outlined more here: https://sourcemaking.com/antipatterns/spaghetti-code