Message-ID: <1108189860.1845.1427457825982.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1844_1066077483.1427457825982" ------=_Part_1844_1066077483.1427457825982 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Spaghetti Design is like having high complexity at the project architecture level, rather than = in a single method or file. That shift from the micro to the macro makes it= so much worse, because now instead of trying to take in a single large met= hod and keep it all in your head, you've got to comprehend the convolutions= of an entire project.
New developers on the team (and even some developers who've been on the = project a while) will have a hard time understanding how the project is org= anized, and where new code should be put. And if they have a hard time unde= rstanding it, they'll have an even harder time successfully modifying it, a= nd using its existing methods, structures, and utilities. Best case, they'l= l make a hash of any new code, which will quickly be caught in testing. Wor= st case, they'll perpetuate the madness by creating their own redundant str= uctures and utilities.
Several ways to hunt for bad design and architecture are available: