How Much Spaghetti Is Too Much Spaghetti?
TL;DR: Spaghetti code becomes a problem when changing one thing regularly breaks three things you did not know were connected.
Messy software is not automatically bad software. Plenty of profitable companies run on systems nobody would frame and hang on a wall. The trouble starts when nobody can predict what a change will affect, when testing becomes unreliable, when fixes create new bugs, and every new feature takes longer than the last. That is the point where mess stops being cosmetic and starts charging interest. You do not have to untangle every noodle. You do need to know which ones are wrapped around the business.
How Much Spaghetti Is Too Much Spaghetti?
Six quick questions about what happens when your team changes the software. This is less about pretty code and more about whether change has become unpredictable.
Answer the questions to see how tangled things are.
The goal is not to judge whether the code is elegant. It is to find out whether software complexity is making change slower, riskier, or harder to predict.