Thirteen Years of Bad Game Code

Re:Thirteen Years of Bad Game Code by icebraining on Friday March 31, 2017 @10:14AM (#14003974)

A far more dangerous mindset is to think that when starting the problem you are capable of planning the perfect architecture up-front.

This sounds off to me; if you assume you'll need to change the architecture later on, aren't you better off starting with a decoupled system that can more easily be changed? Or are you essentially arguing for YAGNI, in the sense that decoupling upfront is potentially useless?

[ Parent | on HN ]

Re:Thirteen Years of Bad Game Code by wtetzner on Friday March 31, 2017 @02:57PM (#14006976)

> aren't you better off starting with a decoupled system that can more easily be changed?

I think the problem is that you don't know where the boundaries of your abstractions should be until you have a better understand of what it takes to solve the problem.

[ Parent | on HN ]

Re:Thirteen Years of Bad Game Code by grey-area on Friday March 31, 2017 @01:51PM (#14006234)

Yes, YANGNI. Not against all decoupling at all, but beginners tend to err on the side of too much structure.

[ Parent | on HN ]