When developers complain about the messiness of a codebase they're asked to maintain, chances are that they are dealing with a "Big Ball of Mud" or "Spaghetti code". This means that the codebase has grown into an uneven or chaotic structure of modules. This happens naturally on long-lasting codebases in which developers had to integrate evolutions quickly, and lacked time, skills and/or alignment with stakeholders.

How to visualize the structure (or lack thereof) of a codebase? How to detect problematic patterns? (E.g. circular dependencies, to name one of those) And how to fix these structural issues?

In this talk, we'll find answers to these questions by exploring an open source codebase and proposing possible remediation strategies.