What to Do When Your Colleague Creates Spaghetti Code

Re:What to Do When Your Colleague Creates Spaghetti Code by Ace17 on Friday September 16, 2016 @01:16PM (#12515567)

Should a well-designed codebase contain special places where "things really happen"? What about the other places then?

[ Parent | on HN ]

Re:What to Do When Your Colleague Creates Spaghetti Code by michaelfeathers on Friday September 16, 2016 @06:30PM (#12517851)

I think the 'ravioli code' moniker is really a slight on good code. It just takes some time to become acclimated to the style of having many smaller pieces. That said, over-engineering is real. Unnecessary layering should go away.

[ Parent | on HN ]

Re:What to Do When Your Colleague Creates Spaghetti Code by Pica_soO on Sunday September 18, 2016 @05:14AM (#12524533)

I think the 'spaghetti code' moniker is really a slight on good code. It just takes some time to become acclimated to the style of having one long codeflow path. That said, over-engineering is real. Unnecessary assembly should go away.

[ Parent | on HN ]