[Discussing article title, not article] I have thought about spaghetti code.. spaghetti is.. * Messy. * Disorganized. * Every part of it is connected to ever

[Discussing article title, not article] I have thought about spaghetti code.. spaghetti is.. * Messy. * Disorganized. * Every part of it is connected to every other part. The third one is the actually really bad one. U tug on one thing and it affects another thing and so on. I call my code rice code, its like spaghetti code but its made of tiny little modules and no part is connected to another. It also (like spaghetti) has no order / design patterns n stuff. Imo committing to a design pattern is kind of a mini-failure cus your project is now less flexible, you've committed to a certain pattern and everything in future has to follow it. Maybe the next feature does not fit well into this pattern. Ideally you can get to end of project without ever committing to one. (But sometimes u give in and use one to overcome a difficult problem)