It’s Only Pasta: a Few Tips on Software Architecture to Avoid Spaghetti Code
summary
Argues that three concrete architectural practices — overview, coherence, balance — cut spaghetti code by focusing on essentials, grouping similar components, and choosing middles, not extremes. Demonstrates with a pair of descriptions (simple label "sorting algorithm" vs a long, noisy spec) to show why distilling essentials aids design. Gives actionable balances: enough program analysis to avoid blind coding but not analysis paralysis, refactor pragmatically, and optimize only relevant hotspots; slides and materials at lucteo.ro.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:42Overview
- 4:23The Dichotomy
- 5:05The Takeaway
- 7:51Coherence
- 9:05High Coherence
- 11:02Balance
- 13:13Application
- 14:48Conclusion
related talks
49mGetting a handle on software architecture
08mLightning talks – 101 Things Software Never Learnt
07msoftware architecture vs code
45mFive things every developer should know about software architecture
57mCore Software Design Principles for Programmers
42mSoftware Architecture vs Code
25mBuilding Castles, Not Sandcastles: Strategies for Software Architecture Success
46mPractical (a.k.a. Actually Useful) Architecture