TerrariaClone – An incomprehensible hellscape of spaghetti code

Re:TerrariaClone – An incomprehensible hellscape of spaghett... by vog on Friday October 13, 2017 @04:13AM (#15463957)

> There is a saying that any complex project will end up mimicking the communication structure of your organization. I must confess I thought it was silly until I realized it happened to us.

Is this necessarily a bad thing? I know this quote and it always made a lot of sense for me. But I never understood where exactly is the problem, and why one should go to great lengths to avoid this.

Moreover, in this concrete example, isn't assigning modules to individual developers (as opposed to collective code ownership) essentially the same? i.e. structuring the code along the organization communication structure?

[ Parent | on HN ]

Re:TerrariaClone – An incomprehensible hellscape of spaghett... by AndrewDucker on Friday October 13, 2017 @04:26AM (#15463992)

They aren't saying it's bad. They're saying it happens. And that you need to be aware of that if you want your code to end up maintainable.

[ Parent | on HN ]

Re:TerrariaClone – An incomprehensible hellscape of spaghett... by vog on Friday October 13, 2017 @05:09AM (#15464128)

What does it mean to "be aware" of this? What should one do differently from one would otherwise do?

[ Parent | on HN ]

Re:TerrariaClone – An incomprehensible hellscape of spaghett... by speedplane on Friday October 13, 2017 @05:23AM (#15464174)

It means that poor communication among team members will lead to poor code, and likely a poor or late product.

[ Parent | on HN ]