Macaroni Architecture
Code shouldn't be tangled like Spaghetti, it should be modular like Macaroni!
Try a sample project:
How Macaroni is your code?
| Level | Score | Description |
|---|---|---|
| 🧀Macaroni | 84-100 | Excellent modularity, clean architecture |
| 🥗Ziti | 67-83 | Well-structured, minimal coupling |
| 🍲Rigatoni | 51-66 | Decent modularity, moderate coupling |
| 🥘Penne | 34-50 | Some structure emerging, room for improvement |
| 🍜Fettuccine | 17-33 | Many entangled dependencies, needs refactoring |
| 🍝Spaghetti | 0-16 | Highly tangled, numerous cross-dependencies |
What's this all about?
Ever looked at a codebase and thought "wow, this is a mess"? Yeah, me too. That's where Macaroni Architecture comes in.
This tool analyzes your code and generates a Design Structure Matrix (DSM) — basically a visual grid that shows how your files depend on each other. It's like a map of your codebase's spaghetti factor.
The goal? Turn your tangled spaghetti code into nice, modular macaroni. Each file should be its own little piece, not glued to everything else. The DSM helps you spot problematic dependencies and refactor towards cleaner architecture.
Just paste a GitHub (or any Git) repo URL, and you'll get a score from 🍝 Spaghetti (yikes) to 🍝 Macaroni (chef's kiss). The matrix shows you exactly where the mess is so you can fix it.