Thirteen Years of Bad Game Code

Re:Thirteen Years of Bad Game Code by zeroxfe on Friday March 31, 2017 @10:27AM (#14004103)

You know you can actually improve year-over-year without chasing a new fad.

(I'm saying this as someone who's been coding in C++ for over two decades, while still finding lots of room for improvement in my older code.)

[ Parent | on HN ]

Re:Thirteen Years of Bad Game Code by osullivj on Friday March 31, 2017 @10:32AM (#14004156)

25 years of C++ myself. Back in the 90s I coded up all the grossest memory management blunders many times over. Long time since I produced one of those; these days I'm capable of producing some exquisitely subtle synchronisation and threading bugs ;)

[ Parent | on HN ]

Re:Thirteen Years of Bad Game Code by laythea on Friday March 31, 2017 @12:55PM (#14005679)

I think the key is to study principles/concepts, not implementations.

[ Parent | on HN ]

Re:Thirteen Years of Bad Game Code by cestith on Friday March 31, 2017 @02:23PM (#14006541)

One should have a solid grounding in principles and concepts. Try shipping principles and concepts at the end of the quarter, though.

[ Parent | on HN ]